Timeline for Optimizing 2x 1.8GB tables takes 50 minutes
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 22, 2022 at 23:14 | vote | accept | adrianTNT | ||
| Dec 22, 2022 at 5:37 | comment | added | Rick James | It knows how to do FULLTEXT against the entire table; it does not know how to check 2 rows for text. The FT index is an "inverted" index. | |
| Dec 22, 2022 at 4:33 | comment | added | adrianTNT |
I see EXAPLAIN says POSSIBLE KEYS: url_hash,url_meta_index; KEY: url_meta_index, does it use the second index (which is way larger) and not narrow rows by url_hash first ?
|
|
| Dec 22, 2022 at 4:22 | comment | added | adrianTNT |
I added the EXPLAIN and EXPLAIN FORMAT=JSON, I ran this on server #2 (of 4) where I know the two url hashes exists in table. It just returns no results if I also do the text bolean search. Or 2 results if I just look for the hashes (first part).
|
|
| Dec 22, 2022 at 4:20 | history | edited | adrianTNT | CC BY-SA 4.0 |
added 1167 characters in body
|
| Dec 22, 2022 at 4:14 | history | edited | adrianTNT | CC BY-SA 4.0 |
added 1167 characters in body
|
| Dec 22, 2022 at 3:56 | comment | added | Rick James |
Please provide EXPLAIN and EXPLAIN FORMAT=JSON on the 'sample query'.
|
|
| Dec 22, 2022 at 3:48 | history | edited | Rick James | CC BY-SA 4.0 |
wrap
|
| Dec 22, 2022 at 2:27 | history | edited | adrianTNT | CC BY-SA 4.0 |
added 573 characters in body
|
| Dec 22, 2022 at 2:05 | history | edited | adrianTNT | CC BY-SA 4.0 |
added 1091 characters in body
|
| Dec 22, 2022 at 1:54 | answer | added | Rick James | timeline score: 1 | |
| Dec 22, 2022 at 1:35 | history | edited | adrianTNT | CC BY-SA 4.0 |
added 172 characters in body
|
| Dec 22, 2022 at 1:30 | history | edited | adrianTNT | CC BY-SA 4.0 |
added 172 characters in body
|
| Dec 22, 2022 at 1:13 | history | edited | adrianTNT | CC BY-SA 4.0 |
added 25 characters in body
|
| Dec 22, 2022 at 0:57 | history | asked | adrianTNT | CC BY-SA 4.0 |