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

Issue 620265 link

Starred by 1 user
Status: Fixed
Owner:
sullivan@chromium.org
Closed: Jun 2016
Cc:
perezju@chromium.org
mythria@chromium.org
█ petrcermak@chromium.org
u...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug-Regression

Blocking:
issue 617117
issue 617133



Sign in to add a comment

Rename old values in TBMv2 memory benchmarks

Project Member Reported by petrcermak@chromium.org, Jun 15 2016 
Please RENAME values across all TBMv2 memory benchmarks according to the
rules specified in the attached 'mapping.json' file (containing a
dictionary mapping old names to new names).

The following benchmarks should be affected:

  Memory-infra:
    * memory.top_10_mobile_tbmv2
    * memory.dual_browser_test

  System health:
    * system_health.memory_mobile
    * system_health.memory_desktop

  Long-running:
    * memory.long_running_idle_gmail_tbmv2
    * memory.long_running_idle_gmail_background_tbmv2

  V8:
    * v8.infinite_scroll
    * v8.infinite_scroll-ignition
    * v8.mobile_infinite_scroll
    * top_10_mobile_memory_ignition
    * top_10_mobile_memory

and migrate the associated ALERTS (if applicable).

I also attached per-benchmark mappings (in case it's easier to do this
on a per-benchmark basis).
mapping.json
100 KB View Download
mapping_memory.top_10_mobile_tbmv2.json
32.0 KB View Download
mapping_memory.dual_browser_test.json
32.5 KB View Download
mapping_system_health.memory_mobile.json
20.0 KB View Download
mapping_system_health.memory_desktop.json
13.5 KB View Download
mapping_memory.long_running_idle_gmail_tbmv2.json
44.7 KB View Download
mapping_memory.long_running_idle_gmail_background_tbmv2.json
5.1 KB View Download
mapping_v8.infinite_scroll.json
9.7 KB View Download
mapping_v8.infinite_scroll-ignition.json
9.7 KB View Download
mapping_v8.mobile_infinite_scroll.json
13.0 KB View Download
mapping_top_10_mobile_memory_ignition.json
19.6 KB View Download
mapping_top_10_mobile_memory.json
19.6 KB View Download

Comment 1 by petrcermak@chromium.org, Jun 15 2016

Cc: perezju@chromium.org u...@chromium.org mythria@chromium.org
Components: Tests>Telemetry
Labels: -Type-Bug -Pri-3 OS-All Pri-1 Type-Bug-Regression
Owner: perezju@chromium.org
Juan: Could you please have a quick look at this before I assign it to Annie?

Comment 2 by petrcermak@chromium.org, Jun 15 2016 

If anyone is interested in seeing which old values are merged into each new value (sometimes there are more due to other past renames), I attached the inverse mapping.
inverse_mapping
88.0 KB View Download

Comment 3 by perezju@chromium.org, Jun 15 2016 

lgtm!

Regarding alerts I'm curious, Annie, could you let us know which alerts are already in place? It might be time to add a few more alerts, e.g., on top_10_mobile_tbmv2.

Comment 4 by perezju@chromium.org, Jun 15 2016

Owner: sullivan@chromium.org
Status: Assigned (was: Untriaged)

Comment 5 by petrcermak@chromium.org, Jun 15 2016 

Annie: Sorry for the huge number of requested renames. Let me know if I can make your job any easier (e.g. by providing the renaming rules in a different format).

Comment 6 by sullivan@chromium.org, Jun 25 2016

Status: Fixed (was: Assigned)
Sorry for the long delay. All the data and monitoring is migrated. Note that there was only monitoring on these metrics for the long-running and v8 tests listed, not for memory infra or system health. If that's not intended, maybe we should file a separate bug to do an audit?

Comment 7 by petrcermak@chromium.org, Jun 27 2016 

Thanks a lot, Annie! I confirm that there should have been no alerts on memory-infra and system health benchmarks.
►

Sign in to add a comment