-
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
pg_table_is_visible slower in CockroachDB 23.1 #108334
Comments
Hello, I am Blathers. I am here to help you get the issue triaged. Hoot - a bug! Though bugs are the bane of my existence, rest assured the wretched thing will get the best of care here. I have CC'd a few people who may be able to assist you:
If we have not gotten back to your issue within a few business days, you can try the following:
🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
Would it be possible to see the entire statements that are slow? |
I've added them in the issue description. |
Disabling the join hint in the |
@DrewKimball could you say more about how you tested that? I tried the change in this draft PR #109377, and did not see much difference. From runnning
|
I just ran them manually on a local cluster on my machine - I didn't know we already had them in a benchmark. Though, I'm not sure that the benchmark is reproducing the issue, |
Yeah maybe. Do you remember what you did manually in your local cluster to manifest this slowness? |
I didn't do anything in particular, but at the time I would have likely had the tpcc and tpch databases loaded. So, it might come down to the number and complexity of tables? |
Describe the problem
The Django test suite takes 60-65 minutes with CockraochDB 23.1.x compared to 40-45 minutes with CockroachDB 22.2.x. Some attempts at improving performance were #93955 and #100871 but the issue remains.
To Reproduce
Running the
inspectdb
Django test app as an example (./runtests.py inspectdb --settings=test_roach
), the run time went from 31 seconds in 22.2.x to 40 seconds with 23.1.x. I turned on slow query logging to 1ms to log all queries. Then I wrote a script to parse the logs and group similar queries. 8 seconds of the 9-second performance difference are attributed to five groups of queries that usepg_table_is_visible
.Queries that include
pg_table_is_visible
when runninginspectdb
test app:Full queries:
Environment:
Jira issue: CRDB-30428
The text was updated successfully, but these errors were encountered: