-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sql: revive BenchmarkTracing #62118
sql: revive BenchmarkTracing #62118
Conversation
5cacaaa
to
209b26a
Compare
(bump) |
pkg/sql/exec_util.go
Outdated
// debugForceRealSpans can be used to force the use of real tracing spans for | ||
// every statement. It's used primarily to measure the tracing overhead in | ||
// BenchmarkTracing. | ||
var debugForceRealSpans = settings.RegisterBoolSetting( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May I suggest a debug knob instead of a cluster setting. The cluster setting increases the chance that users will shoot themselves in the foot.
209b26a
to
ed216e9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @knz and @tbg)
pkg/sql/exec_util.go, line 196 at r1 (raw file):
Previously, knz (kena) wrote…
May I suggest a debug knob instead of a cluster setting. The cluster setting increases the chance that users will shoot themselves in the foot.
Done.
08a2d62
to
dffba28
Compare
dffba28
to
20356ec
Compare
Fixes cockroachdb#62081. It had rotted after we removed the trace.mode setting. It now makes use of a testing knob if enabled, installs real spans all sql statements. We'll defer the actual investigation into the cause of the slow-down in future PRs (prototyped in cockroachdb#62227). $ make bench PKG=./pkg/bench TESTFLAGS='-benchtime=10000x -count 20' \ BENCHES='BenchmarkTracing' BENCHTIMEOUT=50m > benchmark-tracing.txt $ cat benchmark-tracing.txt | grep -v tracing=t | sed 's/tracing=f\///' > old.txt $ cat benchmark-tracing.txt | grep -v tracing=f | sed 's/tracing=t\///' > new.txt $ benchstat old.txt new.txt name old time/op new time/op delta Tracing/Cockroach/Scan1-24 382µs ± 2% 412µs ± 8% +7.68% (p=0.000 n=10+10) Tracing/Cockroach/Insert-24 579µs ± 2% 609µs ± 6% +5.10% (p=0.000 n=10+10) Tracing/MultinodeCockroach/Scan1-24 799µs ± 2% 885µs ± 1% +10.76% (p=0.000 n=10+9) Tracing/MultinodeCockroach/Insert-24 1.09ms ± 1% 1.14ms ± 2% +5.04% (p=0.000 n=9+10) name old alloc/op new alloc/op delta Tracing/Cockroach/Scan1-24 25.3kB ± 5% 32.0kB ± 4% +26.55% (p=0.000 n=10+10) Tracing/Cockroach/Insert-24 38.0kB ± 6% 42.2kB ± 5% +11.02% (p=0.000 n=10+10) Tracing/MultinodeCockroach/Scan1-24 77.7kB ± 8% 97.1kB ±12% +25.05% (p=0.000 n=10+10) Tracing/MultinodeCockroach/Insert-24 107kB ± 8% 115kB ± 7% +7.66% (p=0.023 n=10+10) name old allocs/op new allocs/op delta Tracing/Cockroach/Scan1-24 256 ± 1% 280 ± 1% +9.10% (p=0.000 n=9+9) Tracing/Cockroach/Insert-24 301 ± 2% 321 ± 1% +6.64% (p=0.000 n=10+10) Tracing/MultinodeCockroach/Scan1-24 787 ± 2% 921 ± 2% +17.04% (p=0.000 n=9+9) Tracing/MultinodeCockroach/Insert-24 748 ± 1% 805 ± 2% +7.61% (p=0.000 n=9+9) Release note: None
20356ec
to
af9e646
Compare
bors r+ |
Build failed (retrying...): |
Build failed (retrying...): |
Unrelated flakes. bors r+ |
Already running a review |
Build failed (retrying...): |
Build succeeded: |
Fixes #62081. It had rotted after we removed the trace.mode setting. It
now makes use of a testing knob if enabled, installs real spans all sql
statements. We'll defer the actual investigation into the cause of the
slow-down in future PRs (prototyped in #62227).
Release note: None