Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • 2
    "Queues don't allow you to process more messages; they act as a buffer to help even out the flow and prevent failures when the incoming volume spikes" - Big thanks for sharing this tip. Now I am getting how queues help to streamline the load. Commented Jul 19, 2021 at 17:31
  • @JeganBabu I'm glad it helped. You might want to post a new question about your downstream bottleneck. Those kinds of questions tend to get a lot of answers. Commented Jul 19, 2021 at 17:38
  • Queues can help one to process more messages if the downstream side processes messages intermittently, and the peak rate at which the upstream side can supply messages is lower than the peak rate at which the downstream side can accept them. When connecting some older dot matrix printers to computers with slow printer ports, adding a queueing print buffer could increase the speed of high-resolution graphics printing by about 25-50% because the printers couldn't accept data while they were printing. Without an added print queue, a computer would have to wait while a line was output... Commented Jul 20, 2021 at 5:54
  • ...before it could start sending data for then next line. If peak rate of the buffer's downstream connection was faster than the peak rate of the computer's connection, having the computer load up the buffer while the printer output a line would make it possible for the buffer to feed the next line to the printer faster than the computer could have done, thus reducing the amount of time the print mechanism is waiting for data. Commented Jul 20, 2021 at 5:56
  • 1
    @TheRubberDuck I probably wasn't clear: the volume of the lake is equal to the total volume of water that has flowed in minus the total volume that has flowed out. (I'm ignoring evaporation etc. to keep things simple.) Likewise, the depth of a queue at any point is the total messages that have been added minus the total messages removed at any point in time. Commented Jul 20, 2021 at 14:31