Client side optimizations should record data savings separately from server side |
|||
Issue descriptionData savings should be tracked independently for data savings from using the server optimizations and data savings from using client-side optimizations.
,
Oct 28 2016
This can be revisited once a client-side implementation has a data savings. This is partially implemented and landed, but is lower priority until there is a consumer.
,
Mar 29 2017
,
Mar 29 2017
Can we expand on the bug a bit more? Are there specific savings histograms that we want to compute separately for server optimizations?
,
Nov 8 2017
Closing because I don't know what's needed. Please re-open if there's specific work that you think needs to be done. |
|||
►
Sign in to add a comment |
|||
Comment 1 by bengr@chromium.org
, Oct 28 2016