Re: Optimize: 14 hours and still running!

2005-12-09 Thread Gleb Paharenko
Hello. As was mentioned by other members without seeing your configuration settings it is difficult to say about InnoDB performance. You can indirectly monitor the OPTIMIZE speed by ROW OPERATIONS section of SHOW INNODB STATUS. For InnoDB it maps to ALTER TABLE, which rebuilds the table.

Re: Optimize: 14 hours and still running!

2005-12-09 Thread Eric Bergen
Is the box swapping? Gleb Paharenko wrote: Hello. As was mentioned by other members without seeing your configuration settings it is difficult to say about InnoDB performance. You can indirectly monitor the OPTIMIZE speed by ROW OPERATIONS section of SHOW INNODB STATUS. For InnoDB it maps to

Optimize: 14 hours and still running!

2005-12-08 Thread Nathan Gross
On a 1.6ghz, 1gb ram, Linux machine running Mysql 4.1x. I have an Innodb table with over 20 million records and index size about 3.7 gig, data size 2.2gig (yes, many indexes, more space then the data itself). Last night I tried an Optimize from the Admin gui console (logged in as root at the

Re: Optimize: 14 hours and still running!

2005-12-08 Thread Robert L Cochran
I do not know the answer to this. I do think your machine is slow, and has too little memory. For such a large database you should have a faster processor and more memory. But, I cannot speak to how the Optimize action works. Bob Cochran Greenbelt, Maryland, USA Nathan Gross wrote: On a

RE: Optimize: 14 hours and still running!

2005-12-08 Thread Jeff McKeon
-Original Message- From: Nathan Gross [mailto:[EMAIL PROTECTED] Sent: Thursday, December 08, 2005 13:58 To: mysql@lists.mysql.com Subject: Optimize: 14 hours and still running! On a 1.6ghz, 1gb ram, Linux machine running Mysql 4.1x. I have an Innodb table with over 20 million

Re: Optimize: 14 hours and still running!

2005-12-08 Thread Heikki Tuuri
: Thursday, December 08, 2005 8:58 PM Subject: Optimize: 14 hours and still running! On a 1.6ghz, 1gb ram, Linux machine running Mysql 4.1x. I have an Innodb table with over 20 million records and index size about 3.7 gig, data size 2.2gig (yes, many indexes, more space then the data itself