Add UMA for EQT split by multi-tab vs. single-tab |
||||||
Issue descriptionWe could consider 3 tab count buckets: 1 tab, low tab: 2-4, high tab: 5+ OR just 2 buckets: single-tab and multi-tab. EQT is already available on browser side via GRC: https://cs.chromium.org/chromium/src/services/resource_coordinator/observers/page_signal_generator_impl.cc?l=54 https://cs.chromium.org/chromium/src/services/resource_coordinator/coordination_unit/page_coordination_unit_impl.cc?l=129
,
Apr 5 2018
Is this still something we want?
,
Apr 5 2018
,
Apr 6 2018
I think this would be worth doing, probably in UKM, so we can just report tab count and EQT together. It isn't high priority though.
,
May 9 2018
Increasing priority per email thread where it was stated this might better evaluate the impact on responsiveness.
,
Sep 10
Ping. Any update on this?
,
Sep 12
,
Sep 12
Actually I'm moving this back to P3. With Site Isolation plus other architecture changes, EQT becomes less easy to interpret and we should use other metrics such as input delay instead. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ksakamoto@chromium.org
, Dec 18 2017