Timeline for MySQL lock on MEMORY storage engine, when does it apply?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 15, 2016 at 15:26 | comment | added | Cyberlover | Anyway if things start to go south fast I can disable this by changing a single parameter configuration so thats that. Previously I did something similar by mounting the PHP session folder in RAM and never had a problem. But that requires configuration on service level. This is just an alternative I am testing in order to do the same in application level. | |
| Apr 15, 2016 at 15:17 | comment | added | Cyberlover | I choose data varchar(64000) because all other people that already did this on the internet use text to store data. Since text max storage is 64Kb stackoverflow.com/questions/6766781/… I've picked varchar(64000) because it is the equivalent, because MEMORY does not allow text. Also I've been doing some math using this select: stackoverflow.com/questions/9620198/… With 1 register the table weight is 310Kb, with 10 is 610Kb. For 1000 rows I supose it will be 244 Mb. | |
| Apr 15, 2016 at 1:24 | history | answered | Rick James | CC BY-SA 3.0 |