New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 721917 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
█ dskiba@chromium.org
primiano@chromium.org
█ picksi@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
Hotlist-MemoryInfra



Sign in to add a comment

Emit an UMA [and eventually UKM] metric for private swapped memory

Project Member Reported by erikc...@chromium.org, May 12 2017 
Once we start emitting UKMs, we can also emit more granular information. For example, we probably want:

Total Memory Footprint:
  Private Memory Footprint
    Private Resident Memory Footprint
    Private Swapped Memory Footprint
  Shared Memory Footprint
    Shared Resident Memory Footprint
    Shared Swapped Memory Footprint

Or something like that. Or perhaps we'll break down Shared Memory Footprint further, since there are dlls/SOs, COW pages, etc.

We probably want to find the right balance between too much information that no one will ever look at and is very platform specific, and not enough information.

Comment 1 by dskiba@chromium.org, May 12 2017 

I feel that some of those values can be expensive to compute on some platforms. For example on Linux we have VmSwap in /proc/[pid]/status (Private Swapped Memory Footprint), but we don't have an easy way to calculate "Shared Swapped Memory Footprint".

I would just report everything we have per platform, IMHO more numbers is better than less numbers.

Comment 2 by erikc...@chromium.org, May 12 2017

Summary: Emit an UMA [and eventually UKM] metric for private swapped memory (was: Better breakdowns for consistent memory metrics.)
More specifically, the memory ablation study would like a metric for private swapped memory. This is easy to do on non-Windows platforms.

Comment 3 by erikc...@chromium.org, May 12 2017 

This should be straight forward:

Something close to https://codereview.chromium.org/2867213003/ that fills in a differently named field, with slightly different computations.

And then something like this CL to emit UMA metrics: https://codereview.chromium.org/2878923003/
►

Sign in to add a comment