Issue metadata
Sign in to add a comment
|
A zero-to-nonzero to 4% regression in media.android.tough_video_cases at 464546:464658 |
||||||||||||||||||||
Issue descriptionI think cpu usage just started working.
,
Apr 15 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982283122637189680
,
Apr 15 2017
=== Auto-CCing suspected CL author dfalcantara@chromium.org === Hi dfalcantara@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 : dfalcantara Commit : 8ef9faffba78738c37df77a160fea80ee5f604af Date : Thu Apr 13 23:30:05 2017 Subject: 🔍 Update how shared preferences are handled by the widget Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : media.android.tough_video_cases Metric : cpu_utilization/video.html?src_crowd720_vp9.webm Revision Result N chromium@464562 0.0 +- 0.0 6 good chromium@464604 0.0 +- 0.0 6 good chromium@464605 11.0563 +- 0.158416 6 bad <-- chromium@464606 11.4641 +- 0.670077 6 bad chromium@464607 11.6482 +- 0.447814 6 bad chromium@464610 11.2928 +- 0.299865 6 bad chromium@464615 11.1649 +- 0.253884 6 bad chromium@464625 11.3032 +- 0.372701 6 bad chromium@464645 11.428 +- 0.139247 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=video.html.src.crowd720.vp9.webm media.android.tough_video_cases Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982283122637189680 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5880966385500160 | 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!
,
Apr 16 2017
Wouldn't be surprised if this was related to the other regression that was introduced earlier for 711040. Best thing to do for both is probably just move the initialization of the widget to ChromeActivity, or something; there's too many things that ChromeBrowserInitializer is used by.
,
Apr 16 2017
Actually: crouleau: what's going on with that graph? The whole thing looks hosed.
,
Apr 16 2017
Assigning back to crouleau temporarily for an answer to Comment 5; please assign back afterward if there's something I should be doing here. The graph looks like it just fixed itself and returned to where it was before a gigantic gap appeared.
,
Apr 18 2017
,
Apr 18 2017
Agreed with dfalcatara@'s Comment 6: The graph was simply fixing itself. Not sure how that could have been caused by your changelist.
,
Apr 18 2017
Issue 712620 has been merged into this issue.
,
Apr 18 2017
Issue 712616 has been merged into this issue.
,
Apr 18 2017
Issue 712618 has been merged into this issue. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by crouleau@chromium.org
, Apr 15 2017