Dear Sirs and Ladies,
i'm on the way to create some big indexes on a huge MyISAM-table(13G),
using the 'ALTER TABLE ADD INDEX ..., ADD INDEX ..., ...' -Statement.
After mysql copied all data to the temporary #-Tables it slowes down very
much.
A top shows my that it mostly runs in 'D' (uninterruptible sleep) state with
very low
CPU-consumption (~3%). After i thought it was an I/O-thing, i changed disks
to
scsi, that helped, but not that much.
I tuned the key_buffer_size to 3000M in my.cnf - that also helped, but after
it produced about
2.7 G in the #...MYI-File it slowes down and runs into D-states again.
The engine is a 3 Ghz dualprocessor Pentium 3 with 4G memory.
and 5 scsi drives (striped raid) ext2.
MySQL is 4.017 on SUSE 7.2.
The mysld's are the only processes on this engine and creating these indexes
is the
only job they have to do.
The server is not ment to send queries to, just for creating the tables
files.
I'd likke to know, if the above mentioned behaviour is normal and if there
is a
chance to speed up by tuning other parameters or anything else?
I create all indexes in one 'ALTER TABLE'-statement, would it be faster, to
create the indexes
one after the other ?
Is there maybe a 'dirty trick' ? E.g. creating indexes only half way, kille
the process and then repair via myisamchk,
which seems to repair much faster then the mysqld itself.
any help wouldbe very welcome
Klaus
Topaktuelle Consumer-Adressen anmieten www.consumeradressen.de
Diese Mail ist von:
Deutsche Post Direkt GmbH
Beleglese Center Mannheim
Klaus Franz
Manager Abgleichsysteme
Willy-Brandt-Platz 13 Tel. 06 21.129 56 436
68161 Mannheim
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
