Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user
Status: WontFix
Owner: ----
Closed: Sep 18
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment
14% regression in tracing.tracing_with_debug_overhead at 491933:491975
Project Member Reported by primiano@chromium.org, Aug 9 Back to list
See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=753832

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


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

chromium-rel-mac11-air
Status: Assigned

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

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : tracing.tracing_with_debug_overhead
  Metric       : peak_event_size_rate_avg/peak_event_size_rate_avg

Revision             Result                 N
chromium@491932      5879637 +- 882825      21      good
chromium@491975      5893810 +- 800252      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 tracing.tracing_with_debug_overhead

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

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


For feedback, file a bug with component Speed>Bisection
Comment 4 by sullivan@chromium.org, Sep 18 (3 days ago)
Status: WontFix
Bisect doesn't repro.
Sign in to add a comment