Add blog post: Valkey 9.1 benchmark - #611
Conversation
|
Warning Review limit reached
Next review available in: 10 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughChangesA new blog post introduces Valkey Benchmark Guide
Suggested reviewers: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
| Filename | Overview |
|---|---|
| content/blog/2026-08-15-what-is-valkey-benchmark/index.md | Adds a how-to blog post explaining how to tune valkey-benchmark with keyspace size, payload size, pipelining, and cluster mode; no blocking issues found. |
Reviews (2): Last reviewed commit: "fix bash issue" | Re-trigger Greptile
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@content/blog/2026-08-15-what-is-valkey-benchmark/index.md`:
- Around line 63-66: Update the explanation following the valkey-benchmark
command to qualify the resulting key count as applying to an empty database,
note that existing keys may be overwritten, and instruct readers to verify the
actual count with DBSIZE.
- Line 25: Update the command-only code block in the blog content to remove the
shell prompt prefix, leaving valkey-benchmark as the standalone command without
adding output.
- Around line 134-136: Update the cluster-mode example in the benchmark
documentation to include a small command demonstrating --cluster with -c set to
at least the cluster node count, a custom key containing {tag} such as
key-{tag}, and --rfr yes. Use a read command so replica reads are valid, and
ensure the example is directly actionable.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro Plus
Run ID: a4922b6d-f650-42ef-9c46-ddb5577202ab
📒 Files selected for processing (1)
content/blog/2026-08-15-what-is-valkey-benchmark/index.md
Signed-off-by: Dragos Andriciuc <andriciucdragos@protonmail.com>
Add introduction and hook Signed-off-by: Dragos Andriciuc <andriciucdragos@protonmail.com>
Finish adding the draft content, add 3 levers that progressively increase in benchmarking solutions to the reader, add clustering as a nice to have and add CTA Signed-off-by: Dragos Andriciuc <andriciucdragos@protonmail.com>
Signed-off-by: Dragos Andriciuc <andriciucdragos@protonmail.com>
e6b103d to
4856355
Compare
stockholmux
left a comment
stockholmux
left a comment
There was a problem hiding this comment.
Good start! Two big callouts:
- Cover latency
- Work on your summary and CTA.
Update the blog with initial feedback, also refactored a bunch of paragraphs to flow more naturally. Signed-off-by: Dragos Andriciuc <andriciucdragos@protonmail.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Greptile has paused reviews on this repository — it used its 100 free open-source review credits for this billing period. Reviews resume automatically on August 11. To continue before then, an organization admin can keep reviews running past the free credits — those bill as normal usage.
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@content/blog/2026-08-15-what-is-valkey-benchmark/index.md`:
- Line 44: Update the wording in the benchmark explanation so the phrase reads
“real-life production environments,” preserving the surrounding sentence and
meaning.
- Line 90: Update the sentence near the discussion of larger values to say
“network bandwidth usage” instead of “network bandwidth,” while preserving the
surrounding meaning and grammar.
- Around line 155-160: Add a fixed --seed value to the valkey-benchmark starting
command so repeated runs select the same random keys and remain reproducible.
- Line 54: Replace the malformed opening sentence in the benchmark article with
the clear statement that the golden rule of a useful benchmark is to compare
apples to apples, while preserving the subsequent explanation about comparing
Valkey versions or options.
- Around line 157-160: Remove the trailing -q option from the benchmark command
in the article so the combined SET/GET example displays throughput and latency
percentile output consistently with the documented defaults.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro Plus
Run ID: c1af773f-5a9e-44e3-b033-06800c209da6
📒 Files selected for processing (1)
content/blog/2026-08-15-what-is-valkey-benchmark/index.md
- provided a hook after realistic payload transmissions, mentioning the 10/100/1000 byte payloads having the same throughput - in pipelining, mentioned the trade off of the throughput and mentioned per-request latency rising as well. - update CTA with a note for the new q arg and a clearer ending Signed-off-by: Dragos Andriciuc <andriciucdragos@protonmail.com>
2 participants
Description
This PR is a blog post that describes valkey's benchmarking tool. It provides a how to, going through 3 levers that the user can use to benchmark valkey on their system.
Check List
--signoffBy submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.