-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[Jaeger v2] Run benchmarks #4869
Comments
👀giving this a try |
Hey @yurishkuro! Just wanted to confirm if we can start working on this issue now or if we need to wait until the other issues are resolved in #4843. Can you please let me know? |
It does not need to block, it's actually a part of #4843 scope. |
Hey @yurishkuro, I started a WIP repository on running benchmarks on Jaeger - benchmarks. I was thinking of running a docker-compose file for all the individual components (along with Prometheus and Grafana) for easily setting up the different services and getting the metrics. Please let me know if there is a better alternative. |
@h4shk4t docker-compose sounds good. I would rather not have a separate repository, but a |
Hello @yurishkuro I wrote a document on the background and plan of action for running benchmarks. Kindly have a look: https://docs.google.com/document/d/1iDl8LaAJbCjp1qliECdTQvjEcJ8mfBsIII7J0RH7l6I/edit?usp=sharing |
Replacing this with #5768 |
Part of #4843
Objective
jaeger-v2
deployed in similar configurationSteps
tracegen
, collector, some storage backend (preferably remote like Elasticsearch, to avoid noisy neighbor effect)tracegen
This is not a very straightforward ticket, but hey that's how we learn, so I am still going to tag it as
good-first-issue
,The text was updated successfully, but these errors were encountered: