复： 回复： Why is creating indexes faster after inserting massive data
rows?
Honestly, I did not understand that. I did not say anything about being
complicated. What does mysql not use, caching??
Judging by experience, creating a unique index on say, a 200G table could be a
bitter one
- Original Message -
From: Zhangzhigang zzgang_2...@yahoo.com.cn
As i known, the mysql writes the data to disk directly but does not
use the Os cache when the table is updating.
If it were to use the OS cache for reading but not writing, then the OS cache
would be inconsistent with
Ok, thanks for your help.
发件人： Johan De Meersman vegiv...@tuxera.be
收件人： Zhangzhigang zzgang_2...@yahoo.com.cn
抄送： mysql@lists.mysql.com; Karen Abgarian a...@apple.com
发送日期： 2012年5月8日, 星期二, 下午 6:07
主题: Re: 回复： 回复： 回复： Why is creating indexes faster after
Hi,
If MyISAM tables were being written directly to disk, the MyISAM tables would
be so slow that nobody would ever use them.That's the cornerstone of their
performance, that the writes do not wait for the physical I/O to complete!
On May 8, 2012, at 3:07 AM, Johan De Meersman wrote:
Oh... I thought that it uses it's own buffer cache as same as the InnoDB. I
have got a mistake for this, thanks!
发件人： Karen Abgarian a...@apple.com
收件人： mysql@lists.mysql.com
发送日期： 2012年5月9日, 星期三, 上午 2:51
主题: Re: 回复： 回复： 回复： Why is creating indexes faster
