Subject | Re: [firebird-support] Problem with multiple isql sessions |
---|---|
Author | Gerhard Wiesinger |
Post date | 2007-04-22T14:56:54Z |
Ok, works well.
Any ideas for performance optimizations for inserts:
I'm benchmarking:
100x
(10000xinsert into ... (employee table with 2 indexes, 4 columns)
commit;
)
So whole insert is done with 1Mio Rows.
MySQL (with InnoDB) takes 150s, PostgreSQL 190s, Firebird 2.01 as SS: 769s
time isql -noautocommit -u sysdba -p password staff -i test.sql
Any ideas to improve insert performance?
BTW: Some commercial database editions take >1 hour with this benchmark
...
Thnx.
Ciao,
Gerhard
--
http://www.wiesinger.com/
Any ideas for performance optimizations for inserts:
I'm benchmarking:
100x
(10000xinsert into ... (employee table with 2 indexes, 4 columns)
commit;
)
So whole insert is done with 1Mio Rows.
MySQL (with InnoDB) takes 150s, PostgreSQL 190s, Firebird 2.01 as SS: 769s
time isql -noautocommit -u sysdba -p password staff -i test.sql
Any ideas to improve insert performance?
BTW: Some commercial database editions take >1 hour with this benchmark
...
Thnx.
Ciao,
Gerhard
--
http://www.wiesinger.com/
On Sun, 22 Apr 2007, Ivan Prenosil wrote:
>> Ok, I'm doing a
>> SET TRANSACTION WAIT ISOLATION LEVEL READ COMMITTED;
>> in both sessions.
>>
>> But now when I'm doing:
>> Session 1:
>> SET TRANSACTION WAIT ISOLATION LEVEL READ COMMITTED;
>> insert into ....
>> -- sleep here, goto Session 2
>> commit;
>>
>> Session 2:
>> select count(*) from ...
>> -- it hangs here until the commit
>
> Use
> SET TRANSACTION WAIT ISOLATION LEVEL READ COMMITTED RECORD_VERSION;
>
>
>> Firebird should handle this also very well because it has MVCC, right?
>
> Yes, unfortunately default for READ COMMITTED is NO RECORD_VERSION,
> which basically means disabling MVCC.
>
> Ivan
> http://www.volny.cz/iprenosil/interbase/
>