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

Issue 775302 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Oct 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

174.3% regression in media.mobile at 507435:507565

Project Member Reported by hubbe@chromium.org, Oct 17 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 17 2017

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=775302

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=e58799ba220adb702548998c5d8a29a4c1a689ac885706769ac8392cd8f3c1ef


Bot(s) for this bug's original alert(s):

android-one
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 17 2017


=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : media.mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/video.html?src_tulip2.ogg_type_audio_seek


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.tulip2.ogg.type.audio.seek media.mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8965532565115604304


For feedback, file a bug with component Speed>Bisection
Owner: simonhatch@chromium.org
Simon, could you please take a look?
First "early" revision failed with this:

No benchmark named "media.mobile".
Do you mean any of those benchmarks below?
Available benchmarks are:
  loading.mobile                    A benchmark measuring loading performance of mobile sites.
  media.android.tough_video_cases  Obtains media metrics for key user scenarios on Android.
  media.media_cns_cases            Obtains media metrics under different network simulations.
  media.mse_cases                  Obtains media metrics for key media source extensions functions.
  media.tough_video_cases          Obtains media metrics for key user scenarios.
  media.tough_video_cases_tbmv2    Obtains media metrics using TBMv2.
  memory.top_10_mobile             Measure foreground/background memory on top 10 mobile page set.
  power.typical_10_mobile          Android typical 10 mobile power test.
  smoothness.simple_mobile_sites   Measures rendering statistics for simple mobile sites page set.
  system_health.common_mobile      Mobile Chrome Energy System Health Benchmark.
  system_health.memory_mobile      Mobile Chrome Memory System Health Benchmark.
  thread_times.simple_mobile_sites Measures timeline metric using smoothness action on simple mobile sites
  v8.browsing_mobile
  v8.runtimestats.browsing_mobile
Pass --browser to list benchmarks for another browser.

While the later revision ran fine, did this benchmark change names recently?

Comment 6 by hubbe@chromium.org, Oct 17 2017

Cc: crouleau@chromium.org
Yes, I think it did.

Yes, we just renamed media.android.tough_video_cases_tbmv2 to media.mobile. Is there a workaround to get bisection to work after benchmarks are renamed?
Not off the top of my head, no.
Status: WontFix (was: Assigned)
Ah, okay. 

Looks like the problem has recovered anyway.
Labels: Performance-Media

Sign in to add a comment