The first thing to check is either that your key_buffer_Size is too small (if it's a myisam table) or your innodb_buffer_pool_size is too small (if it's a innodb table).
After that, most of the time for alter table depends on disk IO. On decent hardware a rate of 4G/hr is common, so around 6 hours is much more reasonable for your operation. Regards, Gavin Towey -----Original Message----- From: yueliangdao0...@gmail.com [mailto:yueliangdao0...@gmail.com] On Behalf Of ??? Sent: Thursday, December 23, 2010 11:29 PM To: Adarsh Sharma Cc: mysql@lists.mysql.com Subject: Re: 4 days to drop Index Hi. I think you should upgrade your hardware and adjust your mysqld's parameters. Then your job will be fine. David Yeung, In China, Beijing. My First Blog:http://yueliangdao0608.cublog.cn My Second Blog:http://yueliangdao0608.blog.51cto.com My Msn: yueliangdao0...@gmail.com 2010/12/23 Adarsh Sharma <adarsh.sha...@orkash.com> > Dear all, > > Things becomes too lazy when it takes too much time. > > I am suffering from this problem when droping index of size 17.7 GB on a > table of size 24.7 GB. > This table have some more indexes of different sizes. > It takes near about 4 days to drop the index. > > Can anyone Please guide me whether it is fine in MySQL or things needed to > work on. > > > Thanks & Regards > > Adarsh Sharma > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/mysql?unsub=yueliangdao0...@gmail.com > > IMPORTANT: This email message is intended only for the use of the individual to whom, or entity to which, it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are NOT the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the sender immediately and permanently delete this email. Thank you.
