Share our graphite storage solution Promate #554
Replies: 3 comments 2 replies
-
Unfortunately not anything very usable. As while I was working in previous company I thought about doing sort of proper load testing (generating random data that follows real name schema, for that I used to work on creating this https://github.com/go-graphite/gorelka/tree/master/cmd/gorelka-benchmark which generated graphite metrics, but they are not following the pattern :( ) and then replaying the access.log with any load testing tool (almost any can do that). But I haven't managed to finish that up and check if it produce anyhow credible results. Also I won't be surprised that Promate would work better than whatever internal mechanisms carbonapi provides. As one of the main reasons this support appeared in a first place - is ease of use (single binary that just works for simple use cases). |
Beta Was this translation helpful? Give feedback.
-
Hi @faceair Thanks, looks very interesting!
Thanks in advance for answers! |
Beta Was this translation helpful? Give feedback.
-
About benchmark: I had idea to adopt scaled up part of devops tsbs as standard for graphite benchmark metrics - https://github.com/timescale/tsbs |
Beta Was this translation helpful? Give feedback.
-
https://github.com/zhihu/promate
https://victoriametrics.github.io/CaseStudies.html#zhihu
In our experience, promate is a very big performance improvement over whisper & go-carbon! It is also theoretically better than using victoriametrics directly.
@Civil Do you have a dataset or method for graphite storage performance testing ?
Beta Was this translation helpful? Give feedback.
All reactions