Timeline for Join with certain tables causes execution time to skyrocket
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 8, 2022 at 18:25 | vote | accept | Amit Sedai | ||
| Sep 8, 2022 at 7:46 | comment | added | Lennart - Slava Ukraini | @AmitSedai, since this seemed to have solved your problem please make sure that you mark the answer as accepted. | |
| Sep 8, 2022 at 7:34 | comment | added | Amit Sedai | Awesome. Thanks. Changing the data type of entity_id from varchar to unsigned int worked. As you pointed out, the data type inconsistency was the main reason for index poor performance. Thanks again :) | |
| Sep 3, 2022 at 16:19 | comment | added | Rick James | @AmitSedai - I added a discussion of entity_id to my Answer. | |
| Sep 3, 2022 at 16:18 | history | edited | Rick James | CC BY-SA 4.0 | added 378 characters in body |
| Sep 3, 2022 at 5:16 | comment | added | Amit Sedai | I have added show create table for remaining join tables. I do not see collation inconsistency. Are there tuning variables that can be used to improve overall performances for joins? | |
| Sep 1, 2022 at 16:58 | comment | added | Rick James | Please provide SHOW CREATE TABLE for the other tables, too. I suspect that there is a COLLATION inconsistency. | |
| Sep 1, 2022 at 12:21 | comment | added | Amit Sedai | Hello Rick James, I have incorporated your changes and updated the original question. Added some joins. The query time still exceeds 4 minutes. Please see what else may work. | |
| Aug 30, 2022 at 17:54 | history | edited | Rick James | CC BY-SA 4.0 | added 210 characters in body |
| Aug 30, 2022 at 17:42 | history | answered | Rick James | CC BY-SA 4.0 |