Re: Repair with keycache benchmarks
repair with keycache can take orders of magnitude longer than filesort or just sort.
Since you are doing fulltext indexes, it makes sense that the server would perceive that the index file would be very large, so it uses keycache.
You may want to kill that enable keys, and repair the indexes with
myisamchk --sort-recover --tmpdir=/path/to/disks/with/free/space --ft_min_word_len=xxx --ft_xyz tbl_name.MYI
You'll need the ft_XXX options that are in the [mysqld] section of your my.cnf files, or it will build your index incorrectly.
I've had this speed things up from 5 hours down to 40 minutes...
Subject
Views
Written By
Posted
5083
April 16, 2008 10:37AM
Re: Repair with keycache benchmarks
3562
April 16, 2008 12:28PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.