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

[Jaeger v2] Run benchmarks #4869

Closed
4 tasks
yurishkuro opened this issue Oct 20, 2023 · 7 comments
Closed
4 tasks

[Jaeger v2] Run benchmarks #4869

yurishkuro opened this issue Oct 20, 2023 · 7 comments
Labels
good first issue Good for beginners help wanted Features that maintainers are willing to accept but do not have cycles to implement v2

Comments

@yurishkuro
Copy link
Member

Part of #4843

Objective

  • Measure performance differences between traditional Jaeger v1 setup and jaeger-v2 deployed in similar configuration
    • CPU utilization
    • Memory utilization
    • GC pressure / frequency
  • Document / publish results

Steps

  • Design testing setup
  • Prepare setup (scripts) to start required components and monitoring (e.g. prometheus + grafana, unless there is simpler way to measure)
  • Run locally, capture results, publish on this ticket
  • Run on a HW cluster (I can do it if the scripts are easily reusable)

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,

@yurishkuro yurishkuro added help wanted Features that maintainers are willing to accept but do not have cycles to implement good first issue Good for beginners v2 labels Oct 20, 2023
@Pushkarm029
Copy link
Member

👀giving this a try

@Pushkarm029
Copy link
Member

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?

@yurishkuro
Copy link
Member Author

It does not need to block, it's actually a part of #4843 scope.

@yurishkuro yurishkuro moved this to Todo in Jaeger V2 Feb 3, 2024
@h4shk4t
Copy link
Contributor

h4shk4t commented Feb 19, 2024

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.

@yurishkuro
Copy link
Member Author

@h4shk4t docker-compose sounds good. I would rather not have a separate repository, but a benchmarks top directory in this repo, and you can keep a PR open for discussion. Before setting up anything though I suggest writing down a plan of what and how you want to setup & benchmark. That plan by itself would be a valuable artifact already.

@h4shk4t
Copy link
Contributor

h4shk4t commented Feb 24, 2024

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

@yurishkuro
Copy link
Member Author

Replacing this with #5768

@yurishkuro yurishkuro closed this as not planned Won't fix, can't repro, duplicate, stale Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for beginners help wanted Features that maintainers are willing to accept but do not have cycles to implement v2
Projects
Status: Done
Development

No branches or pull requests

3 participants