Well, what seems to happen is the data gets read from the MyISAM table,
gets written back out to disk in the tmpdir, then when it's all done,
gets actually placed in the .MYD file -- it's the back-and-forthing to
disk that I presume is eating a lot of the time.
Not sure what can be done
uot;optimal"
settings for a DB that generally does full table scans on 2M rows ... a
lot of the data can be kept in that 10 GB of memory, if I could only
force MySQL to use it: those BLOB columns are probably killing me.
Any tuning advice would be much appreciated. Thanks.
-- Dossy
--
Dossy
