Add needDrain property

[ronag]

The current way to determine whether a pool needs a drain event before queueing more tasks is a little awkward. Can we add a needDrain proprerty?

if (pool.needDrain) {
  await EE.once(pool, 'drain')
}
pool.runTask()

[ronag]

When does 'drain' actually get emitted? Is it when the queue is empty or when the queue.size < queue.capacity?

[jasnell]

Currently when the queue is empty. The plan has been to go back and revisit that but haven't been able to get to it yet.

[ronag]

That’s doesn’t sound optimal.

[jasnell]

Yeah, it's not the most optimal approach but I haven't really had the opportunity to go back and figure out a more optimal strategy.

[metcoder95]

Which should be the optimal approach?

[metcoder95]

Hey @ronag, I'm planning to revisit this, do you have any suggestion for an optimal approach?

[ronag]

Not really. But I do think #348 is a duplicate of this.

[metcoder95]

I believe that we can have two action paths here:

1. We can maybe start by adjusting the drain method to be triggered once as soon as the queue.size < queue.capacity, in that way we enable continuing work as soon as there is spare capacity to schedule more tasks (this will translate into a major, so we will need to point to next branch for this one)
2. Adding the needsDraincan be used as soon as the maxQueue has been reached. That should cover the requirement to understand when the pool needs to be waited for being drained until schedule a new task