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

Issue 713704 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Identify a list of important memory metrics to track.

Project Member Reported by bccheng@google.com, Apr 20 2017

Issue description

and add them to go/arc++metrics
 
Cc: conradlo@chromium.org
Cc: littlecvr@chromium.org
There are three categories of memory consumption and we will need to track them separately:

1) Browser memory by native heap
2) Browser memory by blink (https://www.chromium.org/blink/memory-team)
3) Android app memory

Mao is investigating the pros and cons of different heap allocation, and whatever workloads he discovered will meet 1). 

For 3) we can track several 1st party apps that Dolphin already tracked.

Comment 3 by krk@chromium.org, May 25 2017

Cc: jinsong@chromium.org

Comment 4 by krk@chromium.org, May 25 2017

Thanks Ben. If there are dashboards that we can track when ramping up releases, please let me know. I can share with the TPMs to make these part of release checklists.

Comment 5 by krk@chromium.org, Jun 2 2017

Cc: stephenlin@chromium.org

Comment 6 by krk@google.com, Jun 12 2017

Cc: josa...@chromium.org

Comment 7 by krk@google.com, Jun 27 2017

Cc: igo@chromium.org
Project Member

Comment 8 by sheriffbot@chromium.org, Jul 19 2017

Labels: Hotlist-Google
Status: Assigned (was: Untriaged)

Sign in to add a comment