-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
spanconfig: investigate slowdown of combined-statements API with span configs #74919
Comments
It's unclear why these tests experience a massive slowdown. Investigating it is tracked as part of cockroachdb#74919. Release note: None
It's unclear why these tests experience a massive slowdown. Investigating it is tracked as part of cockroachdb#74919. Release note: None
This test got a lot slower under the span configs infrastructure, something we're investigating as part of cockroachdb#74919. Until then, prevent this test from spoiling builds. Release note: None
This test got a lot slower under the span configs infrastructure, something we're investigating as part of cockroachdb#74919. Until then, prevent this test from spoiling builds. Release note: None
PS: I'm not actively investigating this. Letting it sit on the SQL Observability board to remind ourselves to address it during stability at the latest. |
Even outside span configs, I think some of these tests need de-flaking. |
For TestStatusAPICombined{Transactions,Statements} I ran the following with and without span configs (i.e. toggling
They both seem to have the same number of total runs under stress. So perhaps something changed since this issue was filed? TestTenantCannotSeeNonTenantStats though I couldn't get past the real error above. List of things to do to close this issue:
|
I'm just going to optimistically close this issue. |
Describe the problem
In #73876 I'm observing a few tests that make use of the combined statements API experience an order of magnitude slowdowns when span configs are enabled.
For now these tests opt out of the span configs infra by disabling the reconciliation job. This issue tracks investigation of the slowdown, and to remove the testing knob.
To Reproduce
With and without #73876, takes ~2s vs. ~20s after.
Jira issue: CRDB-12320
The text was updated successfully, but these errors were encountered: