Timeline for Slow CREATE TEMPORARY TABLE from SELECT in MySQL
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 13, 2015 at 6:58 | vote | accept | Alexey | ||
| Dec 12, 2015 at 2:16 | answer | added | Rick James | timeline score: 3 | |
| Dec 4, 2015 at 14:47 | comment | added | ypercubeᵀᴹ |
Some clients (I think phpmyadmin does this) add a LIMIT 30 or something, so you see results faster but of cousre sending 30 rows is different than sending 24K rows.
|
|
| Dec 4, 2015 at 14:16 | history | edited | Alexey | CC BY-SA 3.0 |
added 3547 characters in body
|
| Dec 4, 2015 at 14:03 | comment | added | Alexey | seems that you're right and most of the time is taken by "Sending data", I'll update my answer with the client info I used and why I was confused. My bad actually. Thanks | |
| Dec 4, 2015 at 13:49 | comment | added | ypercubeᵀᴹ | And you are sure that the query itself takes no more that 1-2 seconds to execute? Did you try it in command line or through phpmyadmin? | |
| Dec 4, 2015 at 13:43 | comment | added | Alexey |
23681 rows. And yes, the exec time is about the same with or without engine=MEMORY. It was without it initially, I thought that specifying MEMORY storage engine would be faster. But that realized it would not after reading one question here. 47 seconds without engine=MEMORY and 2.1 seconds the SELECT itself, just measured
|
|
| Dec 4, 2015 at 13:39 | comment | added | ypercubeᵀᴹ |
How many rows are produce by the query (and written to the temp table)? And if you remove the ENGINE=MEMORY, so the default InnoDB engine is chosen, does it still take 40 seconds? (or more? or less?)
|
|
| Dec 4, 2015 at 13:26 | review | First posts | |||
| Dec 4, 2015 at 13:31 | |||||
| Dec 4, 2015 at 13:25 | history | asked | Alexey | CC BY-SA 3.0 |