[IMPALA-4752] ObjectPool should not do extra dynamic memory allocation

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 2.8.0
• Fix Version/s: Impala 2.9.0
• Component/s: Backend
• Target Version: Product Backlog
• Assignee: Tim Armstrong
• Reporter: Tim Armstrong
• Created: 10/Jan/17 17:16
• Updated: 13/Jan/17 16:30
• Resolved: 13/Jan/17 16:30

Description

The current ObjectPool implementation is inefficient because it allocates a wrapper object for every object stored in the pool. This could potentially double the number of dynamic memory allocations for small objects.

Instead we should rework the class to avoid this. E.g. storing a function pointer instead of the wrapper class.