Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 5 Feb 2013 12:43:13 +0000 (UTC)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12623008.1354965272548.246411.1360068193463@arcas>
In-Reply-To: <JIRA.12623008.1354965272548@arcas>
References: <JIRA.12623008.1354965272548@arcas>
Subject: [jira] [Commented] (DERBY-6011) Derby performs very badly (seems to
 deadlock and timeout) in very simple multi-threaded tests
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571269#comment-13571269 ] 

Knut Anders Hatlen commented on DERBY-6011:
-------------------------------------------

I've checked in the v2 patch on trunk, revision 1442554. I intend to backport it to the 10.9 branch if the nightly regression tests run stably with the fix.

There is a 10.9.2 maintenance release ( http://wiki.apache.org/db-derby/DerbyTenNineTwoRelease ) planned soon that could carry this fix, provided it gets backported to 10.9 before the release candidate is produced. The dates are still unclear, as there were some speed bumps in the process. It might come out in time.

There's also a 10.10.1 feature release ( http://wiki.apache.org/db-derby/DerbyTenTenOneRelease ) that has been suggested some time later this year, but since no one has signed up for managing the release and published a schedule yet, it's probably less likely to get out in time.
                
> Derby performs very badly (seems to deadlock and timeout) in very simple multi-threaded tests
> ---------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6011
>                 URL: https://issues.apache.org/jira/browse/DERBY-6011
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.7.1.1, 10.8.2.2, 10.9.1.0
>         Environment: Lenovo laptop with SSD's, Windows 7, 64-bit, Sun JDK 1.6.xx
>            Reporter: Karl Wright
>         Attachments: derby.log, force-specific-index.diff, manifoldcf.log, prefer-unique-index-v1.diff, prefer-unique-index-v2.diff
>
>
> The Apache ManifoldCF project supports Derby as one of its underlying databases.  Simple tests, however, demonstrate that Derby is apparently deadlocking and timing out repeatedly under multi-thread conditions.  This problem is long-standing, and is not exhibited by any other database ManifoldCF supports, and makes a simple test take between 6x and 12x as long.
> There is a trivial test with demonstrates the problem vs. other databases.  Please do the following (once you have java 1.6+, svn 1.7+, and ant 1.7+ available):
> (1) Check out https://svn.apache.org/repos/asf/manifoldcf/trunk
> (2) Run the following ant target to download the dependencies: "ant make-core-deps"
> (3) Run the Derby test: "ant run-rss-tests-derby" . Note the time required - at least 180 seconds, can be up to 360 seconds.
> (4) Run the equivalent HSQLDB test: "ant run-rss-tests-HSQLDB".  This test takes about 31 seconds to run.
> The output of the Derby test can be found in the directory "tests/rss/test-derby-output".  Have a look at manifoldcf.log, where all long-running queries are reported.  Derby.log is also included, which shows only that during the test's cleanup phase the database is deleted before it is shutdown, which is not pertinent to the performance issue.
> I am available to assist with ManifoldCF, if that seems to be required.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira