Derby
  1. Derby
  2. DERBY-3092

Use java.util.concurrent in TransactionTable to improve scalability

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.3.1.4
    • Fix Version/s: 10.6.1.0
    • Component/s: Store
    • Labels:
      None
    • Bug behavior facts:
      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.

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

        Issue Links

          Activity

            People

            • Assignee:
              Knut Anders Hatlen
              Reporter:
              Dyre Tjeldvoll
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development