New issue
Advanced search Search tips

Issue 694168 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12.4%-49.8% regression in v8.browsing_desktop_ignition at 446382:450642

Project Member Reported by mythria@chromium.org, Feb 20 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=694168

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguIGW9AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmLrwgAkM


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

chromium-rel-mac12-mini-8gb
chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Feb 20 2017


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

Bisect Details
  Configuration: mac_10_12_mini_8gb_perf_bisect
  Benchmark    : v8.browsing_desktop_ignition
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_avg/browse_news/browse_news_reddit

Revision             Result                    N
chromium@446381      82004656 +- 18509780      21      good
chromium@450642      82191947 +- 28236379      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.reddit v8.browsing_desktop_ignition

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

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


| 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 (was: Assigned)
The results are very noisy and the effective_size_avg could be dependent on the timing of gc. The bisect cannot reproduce this regression.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Apr 11 2017


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

Bisect Details
  Configuration: mac_10_12_mini_8gb_perf_bisect
  Benchmark    : v8.browsing_desktop_ignition
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:effective_size_avg/browse_news/browse_news_reddit

Revision             Result                    N
chromium@446381      56930237 +- 29538998      21      good
chromium@450642      59310249 +- 32684732      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.reddit v8.browsing_desktop_ignition

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

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


| 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!

Sign in to add a comment