[ http://issues.apache.org/jira/browse/DERBY-465?page=comments#action_12316384 ]
Sunitha Kambhampati commented on DERBY-465: ------------------------------------------- Derby has some debug properties that can be enabled, to print the lock table information on a timeout. Please see the following link that explains how to do this. http://incubator.apache.org/derby/faq.html#debug_lock_timeout > 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, 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
