Re: MEMORY tables appalling insert performance

[qihua wu]

You have 500 sql per second? that's 2ms for each sql. If the sql distribute evenly in the time slot, then there should be no lock as 2ms to insert/update is long enough for mysql to complete it. Your workload might be something like, idle for some time, and the burst of sql come in and each sql content for the table lock.

And How do you think innodb is not suitable? Innodb has cache, the dirty page doesn't need to be flushed to disk instantly after the page changed. Suppose the cache is large enough to cache all table/index (if one row is 1K, then 100K rows is only 100M), and have innodb flush the less the possible, much less PIO is required