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
Add Redis resource utilization benchmarks #67
Comments
I recommend you do that after this PR is merged: OptimalBits/bull#641 |
Some related results: #69. Unfortunately not a complete Redis util benchmark. See also: results-2017-08-12.json |
Thanks for adding. So it looks like based on the raw results, Bee Queue is still roughly 2x faster than Bull 3.0rc5. Cc @manast |
@bradvogel hmm, more like 1.5x I would say. I am quite happy with the results so far. The concurrency issue is gone which was the most important issue in 3.0. |
Btw. something to consider. Bull has many more .lua files than bq to read and compile when it starts. This time is also computed in the test, could add 0.5 to 1 second to the total benchmark time. |
Youre right - about 1.5x. Not sure about the startup time, but that could have also influenced the tests. Looks like Bull 3rc5 is getting close, and has just fine performance for 99% of queue use cases. |
We updated the benchmarks to show throughput for job processing across different job queues, but didn't instrument or compare their Redis utilization. We should do that.
The text was updated successfully, but these errors were encountered: