Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <664628508.1222436264819.JavaMail.jira@brutus>
Date: Fri, 26 Sep 2008 06:37:44 -0700 (PDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-3885) Latch contention in B-tree on
 multi-core systems
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Latch contention in B-tree on multi-core systems
------------------------------------------------

                 Key: DERBY-3885
                 URL: https://issues.apache.org/jira/browse/DERBY-3885
             Project: Derby
          Issue Type: Improvement
          Components: Performance, Store
    Affects Versions: 10.4.2.0
            Reporter: Knut Anders Hatlen
            Priority: Minor


When you have many concurrent threads accessing rows in the same table via an index, the root of the B-tree becomes a hot spot. Since access to a node in the B-tree is single-threaded (an exclusive latch is held while a binary search is performed on the node) this limits the scalability on multi-core systems. We should try to find a way to allow multiple threads to navigate the B-tree concurrently without blocking each other.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.