Issue metadata
Sign in to add a comment
|
No data received for top_10_mobile_memory from android-nexus7v2 since 416893 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 5 2016
There is data stoppage alert for memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/* but as far as I can tell, the benchmark is running fine on android-nexus7v2 bot. See for example this build: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus7v2%20Perf%20%282%29/builds/2950/steps/memory.top_10_mobile/ Which has this output: "background@@memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg": { "after_http_en_m_wikipedia_org_wiki_Science": { "description": "effective size of v8 in all processes in Chrome", "grouping_keys": { "phase": "background" }, "important": false, "improvement_direction": "down", "name": "memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg", "page_id": 11, "std": 3876.7043735626785, "tir_label": "background", "type": "list_of_scalar_values", "units": "sizeInBytes", "values": [ 2346920, 2343072, 2337876, 2342292, 2337688 ] },
,
Oct 6 2016
The benchmark from the alert, top_10_mobile_memory, was removed at a31a1aaeb51182e61a48834591ec64d858ad9bf1 (Note: this is different from memory.top_10_mobile, still running) |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by majidvp@google.com
, Oct 5 2016