JavaScript

1700 readers

1 users here now

founded 1 year ago

MODERATORS

[email protected]

Why is the sleep duration taking so long in some cases? (lemmy.world)

submitted 1 year ago by iFarmGolems to c/[email protected]

13 comments fedilink hide all child comments

Hi, I need to create a infinite (but breakable) cycle where I can slow down the cycle by awaiting promises inside. While cycle should be able to do this, but as you can see in the image, the duration is all over the place.

Why is this happening? Is there a way to make it close to the original sleep duration?

you are viewing a single comment's thread
view the rest of the comments

[–] JaddedFauceet 5 points 1 year ago (3 children)

Here is the code for anyone else who want to try

async function slowLoop() {
    while (true) {
        console.time('sleepDuration')
        await new Promise(resolve => setTimeout(resolve, 1000))
        console.timeEnd('sleepDuration')
    }
}

It is not suppose to deviate too much. setTimeout will execute whenever possible at / after the given timeout duration. I am getting between 1006 to 1023 on my sysyem

Is your device performance starved during this test?

[–] iFarmGolems 1 points 1 year ago* (last edited 1 year ago) (2 children)

It's not. I am running process lasso tough but doubt that's the issue.

I have Ryzen 5800x3D and tried the code on latest Ms edge (chromium) browser.

Which browser did you try it on? Or did you try to run it in node?

The browser tab was active and focused also.

[–] JaddedFauceet 2 points 1 year ago (1 children)

I have tested the code in both Chrome and MS Edge.

Is anything else running on the same page that you are testing?

You can test this in an empty environment like this: Enter this in your URL, "about:blank" and test the code in the console.

[–] iFarmGolems 1 points 1 year ago

I tried it in about:blank but it does the same. Maybe there is some extension in my browser that slows it down (somehow). Im running tampermonkey but it's not active on any pages I tried this on.

I ran the script in nodejs and everything works perfectly, the sleep time is very close to the original value so it's definitely something inside browser that causes it to lag.