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

Issue 652205 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug

Blocked on:
issue 586148



Sign in to add a comment

Add background cases to system health benchmarks

Project Member Reported by perezju@chromium.org, Oct 3 2016

Issue description

We want to add cases that measure memory usage after loading some pages and then pushing the browser to the background.

The top priority is to have this working for Android.
 

Comment 1 by hjd@chromium.org, Oct 3 2016

Status: Started (was: Assigned)
Project Member

Comment 2 by bugdroid1@chromium.org, Oct 25 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/81b7c28dc5a75396861fca85ace8c1420224af6b

commit 81b7c28dc5a75396861fca85ace8c1420224af6b
Author: hjd <hjd@chromium.org>
Date: Tue Oct 25 11:24:03 2016

Add background stories to MobileSystemHealth

This adds some background stories to the system health
story set. These stories put the browser into the background
before measuring memory use. At the moment these stories are
only enabled for mobile since backgrounding only works on
mobile.

BUG= chromium:652205 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq

Review-Url: https://codereview.chromium.org/2386083003
Cr-Commit-Position: refs/heads/master@{#427320}

[modify] https://crrev.com/81b7c28dc5a75396861fca85ace8c1420224af6b/tools/perf/page_sets/data/system_health_mobile.json
[add] https://crrev.com/81b7c28dc5a75396861fca85ace8c1420224af6b/tools/perf/page_sets/data/system_health_mobile_043.wpr.sha1
[add] https://crrev.com/81b7c28dc5a75396861fca85ace8c1420224af6b/tools/perf/page_sets/data/system_health_mobile_044.wpr.sha1
[add] https://crrev.com/81b7c28dc5a75396861fca85ace8c1420224af6b/tools/perf/page_sets/data/system_health_mobile_045.wpr.sha1
[add] https://crrev.com/81b7c28dc5a75396861fca85ace8c1420224af6b/tools/perf/page_sets/data/system_health_mobile_046.wpr.sha1
[add] https://crrev.com/81b7c28dc5a75396861fca85ace8c1420224af6b/tools/perf/page_sets/data/system_health_mobile_047.wpr.sha1
[add] https://crrev.com/81b7c28dc5a75396861fca85ace8c1420224af6b/tools/perf/page_sets/data/system_health_mobile_048.wpr.sha1
[add] https://crrev.com/81b7c28dc5a75396861fca85ace8c1420224af6b/tools/perf/page_sets/data/system_health_mobile_050.wpr.sha1
[add] https://crrev.com/81b7c28dc5a75396861fca85ace8c1420224af6b/tools/perf/page_sets/data/system_health_mobile_052.wpr.sha1
[add] https://crrev.com/81b7c28dc5a75396861fca85ace8c1420224af6b/tools/perf/page_sets/system_health/background_stories.py
[modify] https://crrev.com/81b7c28dc5a75396861fca85ace8c1420224af6b/tools/perf/page_sets/system_health/loading_stories.py

Is there anything left to do here? Or can we call this done?
Labels: -OS-Android -Pri-1 Hotlist-MemoryInfra Hotlist-GoodFirstBug OS-Linux OS-Mac OS-Windows Pri-3
Owner: ----
Status: Available (was: Started)
Mobile has been addressed.
Desktop remains available, dropping prio.
Blocking: -652203
Components: Internals>Instrumentation>Memory
Project Member

Comment 7 by sheriffbot@chromium.org, Feb 21 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Archived (was: Untriaged)
I don't think there is anybody wanting to make this happen on desktop, also probably this is not such as different scenario (in terms of memory usage) w.r.t. existing foreground stories in desktop.

Let's close and file a new bug if this changes in the future.

Sign in to add a comment