Skip to content Skip to sidebar Skip to footer

Limited Number Of Javascript Promises Is Not Working If Running In Infinite Loop

My idea is. I have limited number of workers. This workers must do some job. When worker done with job, then he must take other job, until complete all the jobs. I write this code:

Solution 1:

In javascript the event loop is only processed when there is no javascript code left to process. This is because javascript is single threaded. Therefore the event loop cannot be processed in parallel with javascript code. The basic structure of the interpreter is:

       execute javascript code ----------->  process event loop
                   ^                                 |
                   |                                 |
                   '---------------------------------'

In light of this, an infinite loop in javascript code means the event loop is never processed.

So what does this have to do with web workers? Well, web workers execute in their own thread therefore they will run in parallel with the infinite loop. However, the way we get data back from web workers is:

worker.Run(job).then()

And that requires the event loop to run. So while workers can run in parallel with an infinite loop no communications between the infinite loop and the worker will be processed because you're not letting the interpreter the chance to process the event loop.

You cannot use infinite loops in javascript apps.

What to do then?

The solution is to use the event loop. Use setTimeout() or setInterval() if you want periodic asynchronous looping. Or loop by "recursively" calling the function again inside .then() until you run out of things to process.


Post a Comment for "Limited Number Of Javascript Promises Is Not Working If Running In Infinite Loop"