The bits and pieces that belong to the resource coordinator (RC) have come together rather piecemeal over a long time. There is considerable over-generalization in the current service implementation for current needs, and a lot of functionality duplication.
Implementing the RC as a service where all the usage and most of the data is sourced from content and chrome/browser makes it hard to use, and leads to some inefficiencies.
To fix this, the plan is to move the RC graph to /content/browser/resource_manager (or performance_manager), and to consolidate all data representation and all policy as direct clients of the RC graph.
See https://docs.google.com/document/d/1NunGFCglM11FnI27K4GtMeG_RO7O-pikg7Mp4E3asCY/edit?usp=sharing, for a high-level discussion of the end goal and a plan for how to stage the refactoring.
Comment 1 by bugdroid1@chromium.org
, Nov 30