Hi Eric, I think for ALTER TABLE ... ENABLE KEYS, myisam_sort_buffer_size is all that matters. Not sure about key_buffer...
But myisam_sort_buffer is, AFAIK, only used during "Repair by sort" (in PROCESSLIST), not "Repair with keycache." What did yours say during the 21 hours? It may change from sort to keycache after awhile -- something to do with the size of the indexes or something. Not exactly sure about the criteria. No idea about InnoDB, but I would guess that it'd be slower? Does DISBALE/ENABLE KEYS even do anything with InnoDB, or just MyISAM? Hmm. Matt ----- Original Message ----- From: "Eric Jain" To: "mysql-general" <[EMAIL PROTECTED]> Sent: Wednesday, November 05, 2003 5:11 AM Subject: Re: LOAD DATA hangs > > 4) ALTER TABLE ENABLE KEYS -> Puts a full load on the CPU, but neither > > index nor table size seem to change, even after waiting for an hour. > > Based on smaller data sets, I'd expect the index to reach something > > close to 4 GB. > > Update: After several hours, the index file started growing, although > very slowly. After another 21 hours or so the indexes were complete. The > final index file size is 4.43 GB. > > I currently have the following options set: > > key_buffer_size=64M > myisam_sort_buffer_size=64MB > bulk_insert_buffer_size=64MB > > Any suggestions what else could be tried in order to get MySQL to scale? > Any important options I overlooked? Might InnoDB be faster? > > -- > Eric Jain -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
