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

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


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

android-nexus5X

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8973190667370137840

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_google

Revision             Result                  N
chromium@488659      4614028 +- 428516       21      good
chromium@488861      4892945 +- 1177804      21      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 --story-filter=load.search.google system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8973184184775000640

Clicked off bisect with larger range.

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_google

Revision             Result                  N
chromium@488659      4591620 +- 42451.8      21      good
chromium@488874      4881635 +- 1089065      21      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 --story-filter=load.search.google system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Regression seems to be only on that one story but present on a couple of bots.
The benchmark became a lot noisier at the same time as regressing a bit, maybe a timing issue?

+perezju@chromium.org +primiano@chromium.org What do you think, worth pursuing further?

:(

I would love to be able to bisect on stdev, that looks pretty clear even on the bisect output.

I did not spot any obvious telemetry/catapult changes in the range.

The change is small-ish (~350KiB) so it's probably OK to WontFix?