Tuneable parameter 1 request vs. n requests dequeued at a time #24
Description
If a Runner takes a request, doesn't ACK the request, and it dies, the request goes back to the queue and will be pulled by another Runner.
But for performance reasons, sometimes we need to dequeue more than one request at a time because pulling multiple items off the queue is faster. So... what happens if we have to ACK the block of requests and the Runner dies?
Welp... this should be a tuneable parameter and perhaps be based on GET vs. POST (e.g., pull lots of GETs which should be idempotent but one POST at a time)