db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: [jira] Updated: (DERBY-465) Embedded Derby-PointBase comparison
Date Mon, 18 Jul 2005 16:16:26 GMT
I can't tell from your report, are you testing each operation as a
separate transaction?  Any chance you can post your test programs?
If you can't do that, at least the DDL of the table and index
creates would help.

A major difference between derby and some other db's is that by
default it guarantees transaction consistency with each transaction
commit.  This means that it does a synchronous I/O with every
transaction commit, and thus update benchmarks which do one operation
per commit single user are not very interesting as they simply
measure the I/O throughput of the disk.

I don't see in the document what kind of disk you are using. Also for
Derby it is important to list what JVM you used to test.

I would be interested in helping you configure the test as appropriate
for Derby, and am interested at looking at the large DB results.


Peter Kovgan (JIRA) wrote:
>      [ http://issues.apache.org/jira/browse/DERBY-465?page=all ]
> 
> Peter Kovgan updated DERBY-465:
> -------------------------------
> 
>     Attachment: Benchmarks_info_independent.doc
> 
> 
>>Embedded Derby-PointBase comparison
>>-----------------------------------
>>
>>         Key: DERBY-465
>>         URL: http://issues.apache.org/jira/browse/DERBY-465
>>     Project: Derby
>>        Type: Wish
>>  Components: Test
>>    Versions: 10.0.2.1, 10.0.2.0
>> Environment: Windows Server 2003, 4 processors, summary CPU 3.00 Ghz, RAM 1 Gb
>>    Reporter: Peter Kovgan
>> Attachments: Benchmarks_info_independent.doc, Benchmarks_info_independent.doc
>>
>>I have tested 4 major embedded DB.
>>I have found that major disadvantage of Derby is 
>>1)low insert speed and 
>>2)significant performance degradation in select, update, delete  operation speed starting
from some table size.
>>PointBase in comparison has not such degradation.
>>It will be better if you improve your product.
>>Good luck and thank you.
> 
> 


Mime
View raw message