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
  • tracegen, collector, some storage backend (preferably remote like Elasticsearch, to avoid noisy neighbor effect)
  • how long do we need to run, with which throughput determined by tracegen
  • May use this blog as a blueprint: https://medium.com/jaegertracing/making-design-decisions-for-clickhouse-as-a-core-storage-backend-in-jaeger-62bf90a979d (but the objective in this ticket is simpler, we're not trying to find saturation points, just compare relative performance of v1 and v2)
• 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,