[DISPATCH-511] Remove performance problems from locks and memory allocation

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.7.0
• Component/s: Container
• Assignee: Ted Ross
• Reporter: Ted Ross
• Created: 15/Sep/16 18:38
• Updated: 20/Nov/17 18:37
• Resolved: 16/Sep/16 12:29

Description

There are a number of performance issues with locks and memory pooling:

• Locks are not allocated on cache-line boundaries and suffer from false-sharing issues.
• The extra lock checks (checking the acquired state) cause significant overhead. These should be removed.
• Pooled memory objects are not cache-line aligned and suffer from false-sharing
• Memory pool statistics are useful but costly from a performance standpoint. These should be able to be optionally disabled.