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

tsdb: Query and other benchmarks #5875

Closed
gouthamve opened this issue Dec 27, 2017 · 14 comments
Closed

tsdb: Query and other benchmarks #5875

gouthamve opened this issue Dec 27, 2017 · 14 comments

Comments

@gouthamve
Copy link
Member

We don't have proper benchmarks yet and that means we cannot see the potential impact of the changes we are introducing.

@AlekSi
Copy link
Contributor

AlekSi commented Sep 13, 2018

"Help wanted"? How can I help?

@krasi-georgiev
Copy link
Contributor

krasi-georgiev commented Sep 13, 2018

we haven't discussed anything yet so it is a greenfield project, but here some random thoughts.
we already have a benchmarking CI for prometheus and can probably reuse a lot from the logic and pieces.
We can do a very simplified version for the tsdb as well.

  1. Implement some tsdb bench tool.
  2. When a test is triggered it will build and run the versions: one from the PR and another one from master or a release.
  3. Than just use grafana to display the exposed metrics and compare the results.

@sipian and I have worked on the Prombench project so can help along the way as well.

@gouthamve should have some better ideas where to start.

@krasi-georgiev
Copy link
Contributor

not sure if you have looked at the tsdb cli tool, but it already has some benchmarking already so maybe this is a good starting point. Can keep it simple to start with.
https://github.com/prometheus/tsdb/blob/9be883670eaf846e8f5bb65ea577dcd7d28d469e/cmd/tsdb/main.go#L43

@krasi-georgiev
Copy link
Contributor

@AlekSi just found PR: prometheus-junkyard/tsdb#240 that adds some more benchmarking.
I guess our first goal is to somehow automate these and display the results.

The way I see it:

  1. comment /benchmark
  2. Prow starts a job
  3. The job runs go bench against master and another one against the PR and just displays the logs in the prow job dashboard.

@krasi-georgiev
Copy link
Contributor

just came across https://github.com/timescale/tsbs which might help.

@Sangeeta04Sharma
Copy link

Hello contributors, I would like to work on it as my GSOC project. I have used and worked Prometheus, Kubernetes, and Golang. Please guide me and help to start work on it.

@krasi-georgiev
Copy link
Contributor

@Sangeeta04Sharma can you ping me on IRC and will try to give some directions.

@bwplotka bwplotka changed the title Query and other benchmarks tsdb: Query and other benchmarks Aug 13, 2019
@bwplotka bwplotka transferred this issue from prometheus-junkyard/tsdb Aug 13, 2019
@rajibmitra
Copy link

@krasi-georgiev I would like to work on this issue as part of community bridge program if no one is actively working on it.

@krasi-georgiev
Copy link
Contributor

We did this one as part of the last GSOC program. There are still some things to finish, but another contributor has taken the initiative and don't think there is much left to do here to make it an antyre project. I think it landed in the communiyt bridge program by mistake.

@rajibmitra
Copy link

okay , thanks for the update @krasi-georgiev

@brian-brazil
Copy link
Contributor

We have plenty of benchmarks, where do you think there are gaps?

@roidelapluie
Copy link
Member

@brian-brazil I think that #6512 highlights that we probably don't stress enough the tsdb reads.

@imrajdas
Copy link

imrajdas commented Feb 20, 2020

Hi @krasi-georgiev @gouthamve . I would like to take this as my GSOC project. Can you help me with it?

@brian-brazil
Copy link
Contributor

We've looked at this as part of the bug scrub, and we currently have benchmarks in the tsdb for the querier so this is being closed. If there's specific cases not covered, an issue/PR should be created for them.

@prometheus prometheus locked as resolved and limited conversation to collaborators Nov 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants