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

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


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

android-one

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

=== Auto-CCing suspected CL author ericrk@chromium.org ===

Hi ericrk@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Eric Karl
  Commit : 840b7a60cc3c5f802ca271bd167e888e7494e8aa
  Date   : Wed Oct 18 22:39:08 2017
  Subject: [Re-Land] Use GPU Discardable in Image Decode Cache

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : thread_times.simple_mobile_sites
  Metric       : thread_other_cpu_time_per_frame/http___www.ebay.co.uk_
  Change       : 1871.49% | 0.180450081399 -> 3.55755998684

Revision             Result                    N
chromium@509820      0.18045 +- 0.396395       6      good
chromium@509891      0.375312 +- 0.45637       6      good
chromium@509900      0.490853 +- 0.878436      6      good
chromium@509901      0.521861 +- 1.12072       6      good
chromium@509902      3.83169 +- 1.08731        6      bad       <--
chromium@509903      3.73285 +- 1.43435        6      bad
chromium@509905      3.45078 +- 0.564598       6      bad
chromium@509909      4.14339 +- 1.90516        6      bad
chromium@509926      3.93824 +- 1.53215        6      bad
chromium@509961      3.55756 +- 0.736411       6      bad

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=http...www.ebay.co.uk. thread_times.simple_mobile_sites

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

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


For feedback, file a bug with component Speed>Bisection

Ok, making progress. Time moved from the raster thread to the background decode thread. Not sure why, but framerate / smoothness hasn't changed, and overall thread time hasn't changed. It also only seems to have happened in this one test case. Worth understanding, but doesn't seem too concerning.

ericrk: Perf sheriff checking in. Based on #4, and the fact that this was filed a month ago, should we WontFix?

I'd like to fix this eventually, but isn't high priority given that it's not a real regression (just a logging issue), and won't mask future bugs. I think we can drop sheriff.

Confused this with another bug when I responded in #7, per the suggestion in #6, yes, we can close this out.