-
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: regression on EndToEnd/ored-preds #89547
Comments
We should try to get to the bottom of this, but I think this is a pretty minor regression with a very specific edge-case, so it shouldn't block the release. |
The regressions are more mild for me when I run on a GCE worker:
I'l try to bisect to a commit now. |
I was unable to easily bisect this. On many of the commits between the two commits listed in the description, I'm unable to run benchmarks - |
I also ran it on the gceworker with go 1.19.1. |
I'm going to close this. This regression seems very minor and the regressed benchmark is very contrived. We've already made significant improvements to this benchmark in the past, which dwarf this regression. |
Consider the following comparison between 22.1(edc5865) and 22.2(385bf90) of
BenchmarkEndToEnd
frompkg/sql/opt/bench
:(Full comparison is available here. The comparison was made with the following diff on 22.1 SHA:
to allow usage of go 1.19. The comparison was made with
./scripts/bench
that usedmake
under the hood with-benchtime=3s
.)Informs #87685. The regression doesn't seem that severe, so not marking it as a GA-blocker.
Jira issue: CRDB-20298
The text was updated successfully, but these errors were encountered: