At the moment our thread load metrics are wall-time based and measure only time inside scheduler tasks.
Adding thread-time based will allow us to track the total amount of work and the amount of non-scheduling work (e.g. message loop overhead, system events, scheduling overhead, time observers, etc).
Comment 1 by altimin@chromium.org
, Jun 13 2018