🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
Queue outgoing rate setting
Hey team, I wonder if there's a way to change the outgoing rate for a specific queue or the entire cluster?
20+ per second is way too low for our use case.
Comments
-
Outgoing messages are not rate limited by the broker or queue per-se (except for a Standard Edition broker which has a limit of 10000 msg/s of total throughput).
Which SDK / API is the consumer-side application written in? Does the consumer perform one-at-a-time processing, using manual or auto-acknowledgement, and what is the queue setting for "max undelivered messages per flow"?
There are several ways to greatly increase this number depending on which client-side API is being used and what the processing semantics are.
7 -
Thanks @nicholasdgoodman.
I was trying to propagate messages to Azure servicebus, and created all the resources via Connector Wizards with default settings.
I think I've figured it out: I updated the Outgoing Connection Count in the REST Consumer settings, and the outgoing rate jumped from 20+/s to 1200+/s.
3
