Re: data files preallocation

[David Lombardi]

Interesting....

MySQL will be used in an environment where INSERTs occur at a very high rate, around 20 Mb/hour per "user", constantly 24h/7.
During INSERTs , other "users" will connect and SELECT data (SELECTs are known and properly indexed).
MyISAM responded perfectly to this environment because
1) is transaction-less
2) is fast: we tested CPU and disk load with 40 users (800Mb/h) without noticeable CPU usage on mysql service (Windows XP).
3) SELECTs and INSERTs can be executed concurrently (provided that there are no holes in the tables).

Your solution could be a good work-around provided that the 3 conditions above still hold (#3 in particular).

PS:
I'll enter a feature request anyway, since the fragmentation would still occurs on the index files.

Thanks
David



Edited 1 time(s). Last edit at 02/02/2006 05:12AM by David Lombardi.