Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-3092

Use java.util.concurrent in TransactionTable to improve scalability

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.3.1.4
    • 10.6.1.0
    • Store
    • None
    • Performance

    Description

      Running scalability tests with the client and buffer manager from DERBY-2911 shows that access to the TransactionTable.trans (a Hashtable) and XactFactory.tranId (a shared long) are the next major sources of contention.

      Attachments

        1. xact-concept.diff
          7 kB
          Dyre Tjeldvoll
        2. xact-concept.png
          7 kB
          Knut Anders Hatlen
        3. derby-3092-1a-map.diff
          11 kB
          Knut Anders Hatlen
        4. derby-3092-1b-map.diff
          11 kB
          Knut Anders Hatlen
        5. derby-3092-2a-count.diff
          1.0 kB
          Knut Anders Hatlen
        6. derby-3092-3a-xa-visitor.diff
          5 kB
          Knut Anders Hatlen
        7. derby-3092-4a-more-visitors.diff
          16 kB
          Knut Anders Hatlen
        8. derby-3092-5a-dynamic-loading.stat
          0.5 kB
          Knut Anders Hatlen
        9. derby-3092-5a-dynamic-loading.diff
          16 kB
          Knut Anders Hatlen

        Issue Links

        is part of

        Improvement - An improvement or enhancement to an existing feature or task. DERBY-698 Use Java 5 concurrent collections for better concurrency (rather than synchronized collections)

        • Major - Major loss of function.
        • Closed
        is related to

        Improvement - An improvement or enhancement to an existing feature or task. DERBY-4517 Unnecessary synchronization in TransactionTable.add()

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Open

        Improvement - An improvement or enhancement to an existing feature or task. DERBY-2911 Implement a buffer manager using java.util.concurrent classes

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Improvement - An improvement or enhancement to an existing feature or task. DERBY-4478 Use AtomicLong for XactFactory.tranId

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Improvement - An improvement or enhancement to an existing feature or task. DERBY-4512 Avoid unnecessary lookup in transaction table when adding transaction

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Improvement - An improvement or enhancement to an existing feature or task. DERBY-6242 Merge ConcurrentXactFactory into XactFactory

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            knutanders Knut Anders Hatlen
            dyret Dyre Tjeldvoll
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment