Follow up with skordas on 2nd round of perf test to finalize T-shirt sizes and simplify capacity planning for customers. Customers should understand what tempo size to provision for a given load (e.g. traces/second) and how much object storage they need.

•  
• Tempo sizing recommendations (ingested traces) - Test plan 
• Perf/Scale test plan for distributed tracing UI query performance
• UI PERFORMANCE_RESULTS
• DT_UI_performance
• The UI is using the jaeger query API
• The ingestion tests should use query during the test to simulate real deploylement 
• The replica sizes are same for all components - we should be more clever and use higher number only for what makes sense (e.g. ingesters)
• The summary table shows that hardware resources were not fully unitized