Re: MEMORY tables appalling insert performance
Posted by:
qihua wu
Date: December 31, 2009 08:54PM
>>And How do you think innodb is not suitable?
>Because the data is volatile and the IO is quite saturated already.
Now you are using memory tables, right? If so, then why "IO is quite saturated already"?, memory tables don't use IO. Do you have other app consuming lots of IO?
Since the table is small (only 100k), assign the right amount of memory to innodb, innodb doesn't need a IO if change a block as several changes to a block could be combined into one IO.
Daniel, Wu
Subject
Views
Written By
Posted
12489
October 26, 2009 11:46AM
6213
October 26, 2009 03:57PM
5567
December 31, 2009 01:30AM
5369
December 31, 2009 10:20AM
5840
December 31, 2009 01:43AM
5829
December 31, 2009 10:18AM
Re: MEMORY tables appalling insert performance
5341
December 31, 2009 08:54PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.