-
Notifications
You must be signed in to change notification settings - Fork 840
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pika performace #1197
Comments
Just to shed more light into this yet to be explained the huge difference in throughput, I found that using librabbitmq, there's unexplainable message loss meaning not all the messages are received by the messaging queue ( I experimented with 1000000, at the end of the experiment the messaging queue only got 999,820 ) |
@ponach Thank you for the feedback. I don't use librabbitmq in production, but during my tests, I never lost messages. A common error during the tests, is to close the client/connections after the last publish. Btw I really suggest to open an issue with your problem to the |
librabbitmq is not recommended for production. we have a plan for improving py-amqp further as it is more feature-rich and less buggy. |
Yes but I am more interested to understand the performance different |
The only fair comparison here is with |
We can close the issue if you want @michaelklishin @lukebakken |
I am opening this issue after a conversation with @lukebakken
here the thread
RabbitMQ test with different libraries
I made a few tests with different client libraries.
Environment:
Here is the code:
py-amqp
and then
around 18.000 messages per second
librabbitmq
and then
around 102.000 messages per second
Pika
So:
about 11.000 messages per second
Thank you
The text was updated successfully, but these errors were encountered: