0

My site has a query that joins several tables, some with many thousands of rows. When the cache misses, this can leave users waiting for 10+ second queries, sometimes over 20 seconds.

The largest tables involved are event_occurrences and bookings, with approximately 50k rows each. You can view the full query + plan here: https://explain.dalibo.com/plan/1BE.

I added an additional index recently (to event_occurrences.start_time), but the query is still very slow. Perhaps I should add a composite index with id, start_time, and blackout instead? Any other suggestions to speed this query up without a total schema redesign?

Improve this question
0

1 Answer 1

Reset to default
1

It looks like all (99%) of the time is spent doing the sort just before the unique. The unique brings the data set down from 13K rows to 300 so potentially there is room to reduce the data set going into that sort.

Things like using semi-joins or adding join filters might be the way to go so you don’t introduce duplicate results. The join to photos looks to contribute a lot. You could skip the join then load photos separately. - user217655

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.