3.0 embedded on
linux
On 15-6-2016 17:55, chen hsu chen...@outlook.com [firebird-support] wrote:
> Thanks, Helen. Please see my replies inline.
>
> I am sure it is not 3.0 specific, 2.5 is the same. and the main issue is
>
I see. That might be the cause that I did not see throughput increase by adding
more threads. let me try to have each thread create its own dedicated
connection.
To: firebird-support@yahoogroups.com
From: firebird-support@yahoogroups.com
Date: Fri, 17 Jun 2016 12:11:03 -0700
Subject: RE: [fire
Thanks, these tips are very helpful.
#1: has very good improvement, please see the new result below. but will this
turning off of write-barrier cause data loss in case of power loss?
Write-barrier looks about the ordering of journaling transaction content and
commit record, how come it impacts
yes, one connection per database, any thread needs to access this database
would create its own transaction.
To: firebird-support@yahoogroups.com
From: firebird-support@yahoogroups.com
Date: Wed, 15 Jun 2016 21:38:48 +0200
Subject: Re: [firebird-support] performance issue with firebird 3.0 embed
Thanks, Helen. Please see my replies inline.
I am sure it is not 3.0 specific, 2.5 is the same. and the main issue is
scalability, sequential transaction performance is actually pretty good,
comparable to ESE store on windows I was comparing firebird against. but when
running multiple trans
Hi there,
Recently I am doing some performance test on firebird 3.0 embedded used in my
project. The test is pretty straightforward, on one same table, use 100
insertions per transaction as base test unit (creating a transaction, using a
loop to insert 100 records, and committing the transaction
