Read Aloud the Text Content

This audio was created by Woord's Text to Speech service by content creators from all around the world.

Text Content or SSML code:

Hi everyone, Today I’m going to walk through the latency issue we were seeing with the DocLibraryAdd RabbitMQ queue. This problem has been around for quite a while, and clients consistently reported that after completing a task, the document didn’t appear right away. In some cases, the delay was 1 hour, 2 hours, even 3 hours, which was obviously frustrating. The good news is we’ve fixed it. We did a spike to investigate the root cause and explore possible solutions. We identified the main issue, evaluated three different approaches, and implemented the most effective one. I won’t go into every technical detail right now—Ill share the documentation in the chat. If you look at the queue now, you’ll see the Ready message count is 0. Earlier, this number used to be 5k–10k, and sometimes even 40k messages—basically a Black Friday checkout line. Since RabbitMQ processes messages in FIFO order, any Doc Ack task completed by a user would get added to the end of that long queue, leading to the significant delays everyone was experiencing. What we did We increased the number of consumers for this queue from 4 to 12. Based on the queue metrics and current traffic, we calculated that 12 consumers would allow us to process messages effectively in real time. And that’s exactly what’s happening now—no backlog, no hourslong wait. Demo Now I’ll complete a Doc Ack task so you can see that the document appears in the Doc Library almost immediately after the task is completed.