[DERBY-4478] Use AtomicLong for XactFactory.tranId

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.6.1.0
• Fix Version/s: 10.11.1.1
• Component/s: Store
• Bug behavior facts: Performance
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 15/Dec/09 14:48
• Updated: 03/Sep/14 08:31
• Resolved: 15/Jul/13 09:55

Description

Dyre Tjeldvoll posted some results on DERBY-3092 that indicated that some types of load might cause contention on XactFactory.tranId (a shared long), and suggested that it was replaced with a java.util.concurrent.atomic.AtomicLong on the platforms that support java.util.concurrent.*.

I'm splitting this issue out from DERBY-3092 so that the two possible improvements reported there can be addressed independently.

Issue Links

• relates to: DERBY-3092 Use java.util.concurrent in TransactionTable to improve scalability