Add memory metrics when OomIntervention is running to improve triggering |
|
Issue descriptionAdd more UMA to understand the distribution of memory usage (e.g. blink memory usage, renderer pmf, renderer swap & renderer vm usage). This would help improve the triggering threshold.
,
Nov 12
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/60addda9a6277ea88d60df67bc5a51cc90477233 commit 60addda9a6277ea88d60df67bc5a51cc90477233 Author: Yuzu Saijo <yuzus@chromium.org> Date: Mon Nov 12 08:05:43 2018 Report memory reductions because of oom intervention This CL adds new UMAs that report the amount of memory metrics that's reduced as a result of intervention. Bug: 888935 Change-Id: Ie336559f2046f0929830df7bf3b2d35ce7887423 Reviewed-on: https://chromium-review.googlesource.com/c/1319399 Reviewed-by: Steven Holte <holte@chromium.org> Reviewed-by: Kentaro Hara <haraken@chromium.org> Commit-Queue: Yuzu Saijo <yuzus@chromium.org> Cr-Commit-Position: refs/heads/master@{#607169} [modify] https://crrev.com/60addda9a6277ea88d60df67bc5a51cc90477233/third_party/blink/renderer/controller/oom_intervention_impl.cc [modify] https://crrev.com/60addda9a6277ea88d60df67bc5a51cc90477233/third_party/blink/renderer/controller/oom_intervention_impl.h [modify] https://crrev.com/60addda9a6277ea88d60df67bc5a51cc90477233/tools/metrics/histograms/histograms.xml |
|
►
Sign in to add a comment |
|
Comment 1 by bugdroid1@chromium.org
, Sep 27