-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
Tracing Sprint #39, Tracing Sprint #40
The objective of the performance test is to find out an inflection point when the storage starts dropping data.
Requirements:
- monitor system resources: CPU, memory usage
- run for any duration
- monitor dropped spans
- validate spans were stored
- emitted spans should have a similar structure to data emitted by envoy instrumentation
- emitted data should not be static - e.g. values of tags should have high cardinality
There are already these two performance test frameworks:
- https://github.com/jaegertracing/jaeger-performance
- https://github.com/pavolloffay/jaeger-perf-tests
If these cannot be used then we should create something lightweight in go.
Redbull storage doc: https://docs.google.com/document/d/153NHJ9RZttAMbIGUEY8x61W3TZej-jXKjOqOppJiuvc/edit#heading=h.pk20f4i5a4h4