Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Issue 690234 1.9%-2.5% regression in memory.top_10_mobile_stress at 448030:448521
Starred by 1 user Project Member Reported by briander...@chromium.org, Feb 9 Back to list
Status: WontFix
Owner: ----
Closed: Feb 10
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 690276



Sign in to add a comment
See the link to graphs below.
 
Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4597
Failure reason: the build has failed due to infrastructure failure.

Blockedon: 690276

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/http_yandex_ru_touchsearch_text_science

Revision             Result                   N
chromium@448029      57426463 +- 3371776      21      good
chromium@448521      58202499 +- 2831661      20      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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 memory.top_10_mobile_stress

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8988122254795747968

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6579301303975936


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Status: WontFix
Graphs only regressed back to recent values.
Labels: Performance-Memory
Sign in to add a comment