Resend,
Anybody please give me information about different insert performance
between MySQL 5.0.18 and MySQL 4.1.18
as my posting at
http://forums.mysql.com/read.php?22,74279,74279
Thank your
> Heikki
>
> Please see my testing result on MySQL Forum
>
> http://forums.mysql.com/read.php?22,74279,74279#msg-74279
>
> I need explanation about this issue :)
>
>
> Heikki Tuuri wrote:
>
>> Ady,
>>
>> ----- Original Message ----- From: "Ady Wicaksono"
>> <ady.wicaksono@stripped>
>> Newsgroups: mailing.database.myodbc
>> Sent: Monday, March 06, 2006 5:32 PM
>> Subject: MySQL InnoDB Row insert Calculation
>>
>>
>>> With autocommit=1, anybody could give calculation on how many rows
>>> could
>>> be inserted in 1 seconds?
>>
>>
>>
>> I am assuming that you perform a COMMIT after each insert.
>>
>> If the computer does not have a battery-backed disk cache, then the
>> commit speed is limited by the disk rotation speed, which is at most
>> 250 rotations per second nowadays.
>>
>> If the computer does have a battery-backed disk cache (or you take
>> the risk and use a non-battery-backed cache), then the speed is
>> limited by the CPU usage, and for big tables by the disk seek time.
>>
>> If the insertion is CPU-bound, you normally can insert 3000 rows per
>> second, or more.
>>
>> For a big table, several gigabytes or more, inserts to secondary
>> indexes may require disk seeks, limiting the maximum insert speed to
>> 100 rows per second, or less.
>>
>> Best regards,
>>
>> Heikki
>>
>> Oracle Corp./Innobase Oy
>> InnoDB - transactions, row level locking, and foreign keys for MySQL
>>
>> InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up
>> MyISAM tables
>> http://www.innodb.com/order.php
>>
>>
>
>
>
