"Dathan Vance Pattishall" <[EMAIL PROTECTED]> writes:

> #use for when mysql is doing a check or repair
> set-variable    = myisam_sort_buffer_size=64M
>
> to a higher value will make the index happen faster on the fly.

Oops.  I only adjusted the key_buffer value.  Probably I should set
myisam_sort_buffer_size to several hundred megabytes.

If InnoDB indexing doesn't finish either, I'll give it a try (I still
hope that MyISAM tables are more light-weight than InnoDB tables and
result in higher throughput in a many reads/rare bulk updates
scenario).

However, the indexes must be maintenance-free once created (no
"creeping index syndrome").  Can it occur that index pages get lost
during deletion?

> But, for a 100 million row table doing a dump and adding that dump back
> to the db might be your fastest method. Building the index at insertion
> for a self balancing tree is a faster in some cases (I believe this is
> the case) then building one on the fly. 

I don't think this matters much, as reindexing seems to reload the
database anyway.

> My 2 cents. 100 million rows WOW.

I initially hoped to store even a bit more. 8-/

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to