Skip to content
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

Couple of questions #383

Open
pushkarmoi opened this issue Sep 30, 2023 · 0 comments
Open

Couple of questions #383

pushkarmoi opened this issue Sep 30, 2023 · 0 comments

Comments

@pushkarmoi
Copy link

Have some questions related to usage -

  1. Is there a way to "warmup" the target (redis/memcached) and then conduct the actual benchmark?
  2. I tried this tool, and the output "hit-rate" is always 0%. Does it mean that there is no match b/w the inserted and retrieved keys in redis/memcached? What does the hit rate exactly mean?
  3. If i want to benchmark read-only latency ie "get" - is there a way to do so? So far i have modified the config file to only do "sets" and then in a subsequent benchmark do "gets". But since i observed keys are generated randomly - there might not be enough overlap b/w what was inserted and retrieved.

Expected behavior

Questions above

Actual behavior

Questions above

Steps to reproduce the behavior

Not applicable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant