db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Kovgan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-465) Embedded Derby-PointBase comparison
Date Thu, 21 Jul 2005 06:44:46 GMT
    [ http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316316 ] 

Peter Kovgan commented on DERBY-465:

thank you for your comments.
They are all helpful.

1. Really : update is differ and this is my mistake and I'll take care. New tests will be
with the same update in both DB.

2. My second mistake is in last document, describing threads: I tested thread in 100 cycles,
not 10.
(but also PB was tested with 100 loops, so comparison is right for 100 cycles, because I have
no mistake in select)
I also did not indexed PB. PB and Derby are in default configuration. Yes , PB does not write
every transaction in log, but it also tested only for "READ" access in SELECT and here I shouldn't
expect logs? right?

3. Yes, I extend DBOperations for  Derby and for PB, next time I'll send all relevant files
and updated results.

So, excuse me for my mistaken docs.
I hope shortly I'll update them.

> Embedded Derby-PointBase comparison
> -----------------------------------
>          Key: DERBY-465
>          URL: http://issues.apache.org/jira/browse/DERBY-465
>      Project: Derby
>         Type: Wish
>   Components: Test
>     Versions:,
>  Environment: Windows Server 2003, 4 processors, summary CPU 3.00 Ghz, RAM 1 Gb
>     Reporter: Peter Kovgan
>  Attachments: Benchmarks_info_independent.doc, DBOperations.java, Multithreading-access
read.doc, User.java, derby-optimization.doc, derby-pb1.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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message