Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Starred by 1 user
Status: WontFix
Owner: ----
Closed: Feb 10
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 690276

Sign in to add a comment
1.9%-2.5% regression in memory.top_10_mobile_stress at 448030:448521
Project Member Reported by, Feb 9 Back to list
See the link to graphs below.
Bisect failed:
Failure reason: the build has failed due to infrastructure failure.

Blockedon: 690276

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:

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

Is this bisect wrong?

| O O | Visit
|  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