Peter J. Schoenster wrote:
Hi,
I've got a database that is closed to 7G.
I'm using the Standard 4.1.14 version.
The table was corrupt and I had to do a lot of moving of data to free up
enough space on the partition as I discovered I needed at least twice
the database size to do a recover. Well, using myisamchk -o worked. I
then ran "check table" in the mysql client to see what it would say. It
said all was well. I'm just suprised that it took 45 minutes to run.
Anyone run "check table" on large databases? What kind of times did you
encounter? I must say this is on an OLD box ... maybe 512 RAM and right
now I don't now the disk drives used.
45 minutes makes sense. You need more memory for things to go faster,
as caching more of the 7GB database would help things a lot, otherwise
things become disk i/o bound, and that is likely what you are seeing
here. Once you have the extra memory the next step is tuning MySQL
to take advantage of it depending on the storage engine you are using.
Regards,
Josh
--
Josh Chamas
Director, Professional Services
MySQL Inc., www.mysql.com
Get More with MySQL! www.mysql.com/consulting
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
