Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a...
by whakim on Tuesday April 11, 2023 @09:14PM
(#35533853)
I think this is definitely optimal if your jobs take a long time (and if you add in worker autoscaling of some type, you can deal with quick jobs reasonably well too). But if you have a very large number of quick jobs, setting a high prefetch limit can increase throughput by a tremendous amount. It's in this context that multiple queues makes a lot of sense; you can optimize some workers to read from one queue and others to read from another.
[ Parent
| on HN ]
There are no comments on this comment yet.