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

Performance Test Example #367

Closed
vorburger opened this issue Aug 21, 2018 · 4 comments
Closed

Performance Test Example #367

vorburger opened this issue Aug 21, 2018 · 4 comments
Labels

Comments

@vorburger
Copy link
Member

I'm interested in learning more about the performance of jetcd, specifically things like e.g. the maximum number of parallel TXN with a handful of PUT over a relatively large key space per sec.

I'm assuming that there already are performance tests on etcd itself (where, BTW?), and just doing the same through jetcd should lead to similar results - but think it's interesting to anyway exercise it here in this project also, through the JVM and this projects code - agreed? (And it could, later, also be fun to performance profile such a test to see if there are any low hanging fruit obvious performance hot spots anywhere in code in this project...)

I was anyway hoping to do something like this as part of the https://github.com/vorburger/opendaylight-etcd POC some day (after first figuring out the equivalent number of expected size of data and how much change per minute in another existing data store implementation, which that project proposes to replace; to then be able to compare the numbers and see if we have a match or are miles apart), but I guess any code using purely jetcd performance stress testing would best be contributing to this project directly instead.

Please do shout by replying here if this already exists (or is a stupid idea).

@lburgazzoli
Copy link
Collaborator

Please do it :)

@xiang90
Copy link
Contributor

xiang90 commented Aug 25, 2018

see https://github.com/etcd-io/dbtester @vorburger

@fanminshi
Copy link
Member

@vorburger are progress on this?

@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity.
Remove stale label or comment or this will be closed in 7 days.

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

No branches or pull requests

4 participants