Adding Memory.TabFootprint UKM events.
Memory.TabFootprint events give a high-level sample of how much memory is used to render a given URL. To keep these events easy to reason about and analyze, some memory isn't accounted for. Namely, when processes host parts of other tabs, we don't record their contributions. We do, however, make sure that an individual record has all the information nescessary to classify it as a full or partial record. Change-Id: If7a19031502e357be9567ebed760de234f2974ac Reviewed-on: https://chromium-review.googlesource.com/c/1191817Reviewed-by:Kentaro Hara <haraken@chromium.org> Reviewed-by:
Timothy Dresser <tdresser@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Commit-Queue: Tom McKee <tommckee@chromium.org> Cr-Commit-Position: refs/heads/master@{#601136}
Showing
This diff is collapsed.
Please register or sign in to comment