Hello Heikki,
Monday, March 19, 2001, 4:40:30 PM, you wrote:
>>Also the problem with innobase_flush_log_at_trx_commit=0 should be
>>there is no guarantie the last transaction commited will be on it's
>>place if the power would be lost. Also I don't know is it possible in
>>this case for databa
Hi Peter and Christian!
>>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
>>innoba
Hello Christian,
Sunday, March 18, 2001, 12:22:44 PM, you wrote:
>>
>>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
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 e
Hello
I've compiled mysql-3.23.35 with innobase support - it runs much
better than BDB for me - and run a simple benchmark with the
following script:
use DBI;
my $DB= DBI->connect("dbi:mysql:innobase","chris",shift) or die;
$DB->{RaiseError}=1;
$DB->do("drop table if exists speedtest");
$DB->d
