I’m working with ReBus and SQL Server, and I’m trying to understand how the message polling works. From what I can tell, ReBus has two polling modes for consumers: a fast mode when messages are available and a slower mode when there aren’t any for a while.
Does anyone know if it’s possible to tweak these settings? I’m looking for more info on how this system operates. I came across something about a “low-latency mode” for queue polling, but I’m not sure what that means or how to use it.
Can someone explain how to adjust the polling behavior or point me to some detailed documentation about this feature? I want to make sure our setup is as efficient as possible. Thanks for any help!
hey there lucaspixel23! i’m curious about rebus too. have u tried looking into the ‘input queue options’ settings? i think there might be some polling config stuff there. what kinda performance are u aiming for with ur setup? maybe we can brainstorm some ideas to optimize it togethe?
yo LucasPixel23, i’ve messed with rebus before. for tweaking polling, check out the ‘SetInputQueueOptions’ method. u can adjust stuff like ‘maxParallelism’ and ‘prefetchCount’ there. the low-latency mode is prolly what ur after - it keeps polling fast even when no msgs. hope that helps bro!
To configure message polling in ReBus for SQL Server, you’ll want to focus on the InputQueueOptions. These allow fine-tuning of the polling behavior. Key parameters include PeekInterval, which controls how often ReBus checks for new messages, and MaxParallelism, which determines concurrent message processing. For low-latency scenarios, you can set a short PeekInterval and adjust MaxParallelism based on your system’s capabilities. Keep in mind that aggressive polling can increase database load, so monitor performance metrics closely. I’ve found that starting with conservative values and gradually optimizing based on your specific workload yields the best results.