db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <derby-...@db.apache.org>
Subject [jira] Closed: (DERBY-465) Embedded Derby-PointBase comparison
Date Tue, 23 Aug 2005 18:10:11 GMT
     [ http://issues.apache.org/jira/browse/DERBY-465?page=all ]
     
Mike Matrigali closed DERBY-465:
--------------------------------

    Resolution: Fixed

Peter has completed his performance testing effort vs. pointbase and has attached his results
to this issue.
Some of my observations:
o  Derby's default configuration which guarantees transaction consistency, often results in
users believing Derby
     is 10 times slower than other db's like PointBase which default to not syncing their
transactions.  This is often
     the first thing new users see when they write their first program which does inserts
with autocommit true, thus
     committing on every transaction.  My belief is that most applications which use transactions
actually expect to be
     able to count on the commit, but there are a number of applications which don't.
o   Many of the initial problems seen trying to run this benchmark was that there were no
indexes.  It was interesting
      that for 100,000 rows that performance was actually somewhat ok for keyed lookup, even
when there was no index.
      Should a zero-admin database somehow create it's own indexes on the fly?
o    The write portion of this benchmark was sort of unusual in that it updates and deletes
in a concurrent fashion a large
       % of the total data set.  As the number of users was increased this caused deadlocks.
 The conclusion that  only
       a small number of updaters could be supported I believe is because of this particular
application mix.  I have seen 
        Derby support 100's of concurrent readers/writers in a more standard application mix
where the number of rows 
        affected by each user transaction is smaller.

> 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.0, 10.0.2.1
>  Environment: Windows Server 2003, 4 processors, summary CPU 3.00 Ghz, RAM 1 Gb
>     Reporter: Peter Kovgan
>  Attachments: Benchmarks_info_independent.doc, DBBenchmarkProject.zip, DBOperations.java,
Multithreading-access read.doc, User.java, dbbenchmark_multi_user_04_08_2005.zip, 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message