Busy Isolate selection algorithm is too naive

Dreckr / Worker

Utility for easy concurrency with isolates

MIT License

35 stars 10 forks source link

Busy Isolate selection algorithm is too naive #2

Closed Dreckr closed 10 years ago

Dreckr commented 10 years ago

If there is no free isolate, current implementation simply uses the first busy one it finds. This can cause a isolate to be flooded with tasks while others are free.

Dreckr commented 10 years ago

The algorithm has been replaced. Now it selects the isolate that has less tasks in its queue. I'll open another issue proposing Task weight, making possible a smarter algorithm.