At 20:43 Uhr -0600 17.3.2001, Dan Nelson wrote:
>In the last episode (Mar 17), Christian Jaeger said:
>> innobase table:
> > autocommit=0, rollback after each insert: 59 insert+rollback/sec.
>> autocommit=0, one rollback at the end: 2926 inserts/sec.
>> autocommit=0, one commit at the end: 2763 inserts/sec.
> > autocommit=1: 34 inserts/sec.
>>
>> In the last case I can hear the head from the hard disk vibrating, it
>> seems that innobase synches each commit through to the disk oxide.
>> I'm sure innobase isn't the fastest database in the world if this is
>> true for everyone. Why could this be the case for me?
>
>If you are going to be committing on every record, you'll want your
>tablespace and logfile directories on separate disks to avoid
>thrashing. If you only have one disk and don't care if you lose the
>last few transactions if your system crashes, try setting
>innobase_flush_log_at_trx_commit=0 in my.cnf.
Wow, thanks. With innobase_flush_log_at_trx_commit=0, the benchmark now shows:
autocommit=0, rollback after each insert: 1587 inserts+rollbacks/sec
autocommit=1: 2764 inserts/sec.
That's even faster than myisam (2487 inserts/sec today)!!!
ChristianJ
>--
> Dan Nelson
> [EMAIL PROTECTED]
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
