We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While Redi/S performances pretty well against Redis w/o pipelining, real Redis crushes Redi/S when pipelining is on.
helge@ZeaPro ~ $ redis-benchmark -P 100 -p 1337 -t SET,GET -n 500000 -q SET: 53885.12 requests per second GET: 58092.25 requests per second
vs
helge@ZeaPro ~ $ redis-benchmark -P 100 -t SET,GET -n 500000 -q SET: 730994.12 requests per second GET: 1057082.50 requests per second
Redi/S perf just improves ~20% when pipelining is enabled, while Redis does more like a ~120%.
Maybe the key here is to not process the incoming requests one-by-one, but rather in batches. (also only flush in batches).
The text was updated successfully, but these errors were encountered:
No branches or pull requests
While Redi/S performances pretty well against Redis w/o pipelining, real Redis crushes Redi/S when pipelining is on.
vs
Redi/S perf just improves ~20% when pipelining is enabled, while Redis does more like a ~120%.
Maybe the key here is to not process the incoming requests one-by-one, but rather in batches. (also only flush in batches).
The text was updated successfully, but these errors were encountered: