Identify a list of important memory metrics to track. |
||||||||
Issue descriptionand add them to go/arc++metrics
,
May 4 2017
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.
,
May 25 2017
,
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.
,
Jun 2 2017
,
Jun 12 2017
,
Jun 27 2017
,
Jul 19 2017
,
Aug 1
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by conradlo@chromium.org
, Apr 24 2017