New issue
Advanced search Search tips

Issue 680709 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
benjhayden@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

28.6% regression in tracing.tracing_with_debug_overhead at 442240:442574

Project Member Reported by benjhayden@chromium.org, Jan 12 2017 
Looks like several of the stories stopped reporting data briefly, then started back up at a higher memory usage for some reason. Neither the benchmark py file nor the metric js file changed.

Comment 1 by benjhayden@chromium.org, Jan 12 2017 

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

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


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

chromium-rel-win7-gpu-nvidia
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Jan 14 2017 


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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : tracing.tracing_with_debug_overhead
  Metric       : Max event size in bytes per second_min/Facebook

Revision             Result                    N
chromium@442239      11528253 +- 577127        14      good
chromium@442574      19949042 +- 10567097      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=Facebook tracing.tracing_with_debug_overhead

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

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


| 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 Tests>AutoBisect.  Thank you!
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jan 14 2017 


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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : tracing.tracing_with_debug_overhead
  Metric       : Max event size in bytes per second_min/Max event size in bytes per second_min

Revision             Result                   N
chromium@442240      8108163 +- 1867171       14      good
chromium@442574      10477058 +- 1551180      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests tracing.tracing_with_debug_overhead

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

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


| 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 Tests>AutoBisect.  Thank you!

Comment 6 by benhenry@chromium.org, Jul 27 2017

Status: WontFix (was: Untriaged)
This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.
►

Sign in to add a comment