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] Commented: (DERBY-465) Embedded Derby-PointBase comparison
Date Wed, 20 Jul 2005 17:59:46 GMT
    [ http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316259 ] 

Mike Matrigali commented on DERBY-465:

A question on the derby-pb1.doc.  It looks like the update statement used by derby and the
one for pb use 2 totally different fields in the 
update statement.  Is this a problem with the test, or maybe a typo?

For the set of queries described in derby-pb1.doc, derby will need an index created on the
mvalue column, to get reasonable delete/update/select
performance for a large number of rows where the subset of rows determined by the where clause
is a small set of rows.  The original benchmark
you based your work on, did not have any where clause queries so did not need any indexes.
 There is automatically an index on the primary key
you create but none of your queries actually use the primary key.

So far I am at a loss to explain your newest test results.  On similar tests of selecting
all rows from from a table we see results in the 
100,000 rows/second range, on much slower machines than you have.
Your single user result if I read the doc right is reporting 140 seconds for 10 cycles of
100,000 rows.  I would  expect something in the 
5-10 second range.  It looks like you must have a .java file with the actual queries that
extends DBOperations - any chance not the same
test was run against pb and derby? 

> 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