[MESOS-4770] Investigate performance improvements for 'Resources' class.

• Type: Improvement
• Status: Accepted
• Priority: Critical
• Resolution: Unresolved
• Epic Link: allocator performance phase 2
• Sprint: Mesosphere Sprint 32
• Assignee: Unassigned
• Reporter: Benjamin Mahler
• Created: 24/Feb/16 23:12
• Updated: 07/Feb/17 00:36

Description

Currently we have some performance issues when we have heavy usage of the Resources class. Currently, we tend to work around these issues (e.g. reduce the amount of Resources arithmetic operations in the caller code).

The implementation of Resources currently consists of wrapping underlying Resource protobuf objects and manipulating them. This is fairly expensive compared to doing things more directly with C++ objects.

This ticket is to explore the performance improvements of using C++ objects more directly instead of working off of Resource objects.

Issue Links

• is blocked by: MESOS-5700 Add benchmark test for Resource class
• is related to: MESOS-6765 Make the Resources wrapper "copy-on-write" to improve performance.
• relates to: MESOS-5425 Consider using IntervalSet for Port range resource math
• links to: callgrind.out.32445