New answers tagged

0

You can probably do a thousand simple commands on a MEMORY table per second. Can you, the single user, type fast enough to exceed that?? If you can, InnoDB may be the answer. In at least one test, high speed ingestion worked better with InnoDB, presumably because of the differences in locking. Be aware that data varchar(64000) NULL is not efficient in ...


0

You said in your question It makes me think that when you insert/update/replace the table locks itself automatically and entirely so you will not be able to select anything while the write is being done. Is this correct? You are correct. The MEMORY storage engine performs a full table lock for every DML statement. That is why the link you mentioned ...


0

Percona has a github page on the following OPTIMIZE TABLE (which references another Percona Blog) ANALYZE TABLE There is lots of info explaining why. For example, there are messages stored in non-leaf nodes of Fractal Trees. All those messages are pushed way down to leaf nodes. This simplifies retrieval of stats needed by the Query Optimizer. Please ...



Top 50 recent answers are included