Issue metadata
Sign in to add a comment
|
No data received for memory.top_10_mobile_stress from android-nexus7v2 since 433674 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 7 2016
There's no official owner, perezju@ appears to be closest. From a recent run (https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus7v2%20Perf%20%283%29/builds/3604/steps/memory.top_10_mobile_stress/logs/json.output) "after_https_mobile_twitter_com_justinbieber_skip_interstitial_true": { "description": "total effective size reported by Chrome for the GPU process in Chrome", "grouping_keys": { "phase": "background" }, "important": false, "improvement_direction": "down", "name": "memory:chrome:gpu_process:reported_by_chrome:effective_size_avg", "page_id": 13, "std": 118689.25814916866, "tir_label": "background", "type": "list_of_scalar_values", "units": "sizeInBytes", "values": [ 15338668, 15030660, 15084724, 15127052, 15192876 ] }, I'm not sure why this isn't getting reported on the dashboard.
,
Dec 8 2016
TL;DR: It's probably all fine. Assigning to Primiano to double check. All of these are on reported_by_chrome:gpu while on background, and other metrics are still reporting: https://chromeperf.appspot.com/report?sid=df89f3047ac0f6c7b32f7347328454d5756efab4a7b9be6f8b1584eaa19b3613&start_rev=421711&end_rev=436526 So it's probably an expected side effect of Chrome no longer using gpu memory in those cases. It's strange, however, that the gpu metric also vanished on some ref builds, e.g.: https://chromeperf.appspot.com/report?sid=df89f3047ac0f6c7b32f7347328454d5756efab4a7b9be6f8b1584eaa19b3613&start_rev=421711&end_rev=436526 Annie, was there a recent update on ref builds?
,
Dec 8 2016
+aiolos did update the ref build recently
,
Jul 7 2017
the benchmark is no more |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by tdres...@chromium.org
, Dec 7 2016