Live trace/log writers: heavy compression on the producer thread can double total CPU

Profiling a simulation-trace writer showed it used about 2x the CPU of a competing writer on a small design. Nearly all of the gap was compression at a high zstd level (z9) plus encoding, both running on the producer (simulation) thread. The competitor used fast LZ4. Lessons: (1) on small workloads writer CPU dominates total CPU, so ratios look extreme; always show the bucket split (compressor, encoder, alloc, callbacks, workload itself) from perf samples, not only totals. (2) Report user+sys, not user alone: user-only inflated the ratio from 1.9x to 2.1x. (3) The levers, in order: lower the live compression level (z3 measurably closed most of the gap, at some size cost; recompress offline if size matters), move compression to a writer thread off the producer, trim per-event bookkeeping, and defer index-building work to close. (4) Record the compression level and which thread compresses in every benchmark row; otherwise CPU comparisons across tools are not interpretable.