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 08:12:47 GMT
    [ http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316327 ] 

Peter Kovgan commented on DERBY-465:

previous error is result of low derby.locks.escalationThreshold

But I don't understand the reason of this error....
5000 rows is default , if operation affects more then 5000 rows, then DB locks whole table.

but it seems that after whole table was locked, DB attempts to lock single row...

Is it bug?
Or I missed something?

> 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