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 tests - storage backends #990

Closed
jpkrohling opened this issue Aug 14, 2018 · 1 comment
Closed

Performance tests - storage backends #990

jpkrohling opened this issue Aug 14, 2018 · 1 comment

Comments

@jpkrohling
Copy link
Contributor

As a continuation of #989, we also want to exercise a common set of options against different storage backends:

  • Cassandra
  • Elasticsearch
  • Kafka
  • in-memory
  • Any other "supported" backend that might be available at the time of the test

In order to get comparable results, everything should remain the same except the backend configuration. A tricky part is factoring out the network latency from the results, but there are some techniques for that.

Once we have good results about "same everything, different backend", we might also want to compare the same backend with different configuration options, so that we get to know what's the best set of options for a given storage. For instance, Kafka might perform better with more workers and smaller queue size, whereas ES might need a bigger queue size.

@yurishkuro
Copy link
Member

old issue

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

No branches or pull requests

2 participants