roachtest: run some (most?) roachtests with tracing enabled #71663
Labels
A-testing
Testing tools and infrastructure
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
no-issue-activity
O-roachtest
X-stale
Is your feature request related to a problem? Please describe.
We want to see when tracing causes performance pain. One good way to catch these would be to see the overhead in some benchmarks we track. Consider adding a few new roachperf configurations for kv, ycsb, tpcc that have tracing enabled.
Another thought is that maybe for the non-performance-centric we should enable tracing as it may exercise edge cases.
Additional context
Relates to #58610.
Jira issue: CRDB-10707
The text was updated successfully, but these errors were encountered: