cockroachdb / cockroachdb/cockroach
testing: can we OOM proof execution stats with high sql.txn_stats.sample_rate
Open
C-enhancement
O-support
P-3
quality-friday
T-sql-queries
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
Is there a non-roachperf TPCC/TPCH roachtest that we can jack up sql.txn_stats.sample_rate to 100 and make sure none of our execution stats tracing stuff causes OOMs?
Might be good to track throughput and latency too and measure the overhead of this sampling?
Jira issue: CRDB-27846
Contributor guide
Assessment
This issue has not been assessed yet.