Queuing In Practice

A weekly podcast with Cliff Click talking about all things to do with programming, programmers and computer performance.

This is a short talk on my experiences on queuing in practice.


1 thought on “Queuing In Practice

  1. Queues are springs, which are part of the suspension not the power train.

    A couple additional points not addressed in your excellent episode (from my background in web apps):

    1) Queues can buy you time for your system to adapt, such as by bringing additional resources online or by fixing a bug that’s delaying processing. But as you pointed out several times, growing queues are an unstable situation and will eventually lead failure without a change in the system.

    2) Queues allow components with different response time requirements to interact. Example 1, HTTP responses deferring work not necessary for rendering that response by creating a job. Example 2, coalescing multiple updates. This can be useful to amortize transaction costs over the larger number of updates (sacrificing latency for throughput), or for algorithmic requirements such as sorting incoming data before writing (priority queues are useful here, though they should probably be renamed sorting queues).

Leave a Reply

Your email address will not be published. Required fields are marked *