-
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
sql: index over tpcc.public.customer (c_last, c_first) takes a lot more time #34834
Comments
working on this. |
this instance ran fast, but I believe the fundamental problem here is the SSTs are too small. I'm going to work on a change that increases the size of these SSTs |
this problem only happens if this particular schema change is the 3rd one to run. Also note the 4m7s time it took to run count(1) on the table in order to validate it. At a minimum we should be creating fewer SSTs |
35806: sql: speed up index backfill validation r=vivekmenezes a=vivekmenezes use AS OF SYSTEM TIME TO reduce contention with write traffic. related to #34834 Release note: None Co-authored-by: Vivek Menezes <[email protected]>
the validation took many minutes. This table only has 3M rows. |
We have cockroachdb#34834 tracking why a schema change is taking more time. Until that is fixed we'd like to extend this timeout and run the tests reliably so that we can find other problems. Release note: None
35953: roachtest: extend the schema change test timeout by a bit r=vivekmenezes a=vivekmenezes We have #34834 tracking why a schema change is taking more time. Until that is fixed we'd like to extend this timeout and run the tests reliably so that we can find other problems. related to #35734 #35658 Release note: None Co-authored-by: Vivek Menezes <[email protected]>
We have marked this issue as stale because it has been inactive for |
On TPCC-100
CREATE INDEX ON tpcc.public.customer (c_last, c_first)
="CREATE INDEX ON tpcc.customer (c_last, c_first);" took 13m4.242052s
is much slower than
"CREATE INDEX ON tpcc.order (o_carrier_id);" took 1m10.472743s
Jira issue: CRDB-4622
The text was updated successfully, but these errors were encountered: