On Sat, Jul 05, 2003 at 01:03:17PM +0000, James Yang wrote:
> I have a MYISAM table, which is about 2.2G and 19,000,000 records. When I
> create indexs for it, I couldn't finish after 4 hours.
You mean it was still running? Was there still disk or CPU activity
after 4 hours?
> But when I reduce
> the records to 16,000,000, about 1.9G, the same index can be finished
> within 35 minutes. Can anyone explain it? Thanks in advance.
>
That's much shorter than 4 hours!
Maybe your disk was full when creating the 2.2G table's index? MySQL
waits until disk space becomes available again. You wouldn't see much
disk activity while it is waiting.
Keep in mind that MySQL makes a copy of your table while it is adding
the index. You'll need twice the space of your initial table, plus
space for the additional index.
Regards,
Fred.
--
Fred van Engen XB Networks B.V.
email: fred.van.engen@stripped Televisieweg 2
tel: +31 36 5462400 1322 AC Almere
fax: +31 36 5462424 The Netherlands
