askForWork() performance over WAN

[nponeccop]

Now the sequence is:

-> PRE_SLEEP
<- NOOP
-> GRAB_JOB

But to compensate for latency it is better to GRAB_JOB as soon as possible - when job.end() is called. Even before the result is sent, as it could be large so sending it takes significant time.

[iarna]

This sounds totally reasonable.

[amv]

I think this is a good idea.

However it got me thinking: If I want to spin up a worker to do exactly one work (and exit afterwards), what would be the proper code to execute?

Would this change affect this code?

Context: The reason I am asking is the possible rise of the AWS Lambda -style execution model where an isolated container is spun up for each function invocation.

[nponeccop]

I think it's better to have separate API for one-off workers, similar to EventEmitter.once. E.g. registerWorkerOnce