This repository was archived by the owner on Jan 2, 2026. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a connection pooler since I was hitting the connection limit resulting in dropped requests. Things were working nicely, until the thread safety of pika came into play. Thus, I added
add_callback_threadsafein, as well as a few more changes to properly work with the blocking connection in a multithreaded environment.With very spammy users (req every .1-.5 sec), we can handle a pretty high throughput without dropping any requests now. For reference, I wasn't able to get above 30 RPS beforehand
With less spammy users (req every 1-5 sec), but more overall, we start to run into issues