New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 753374 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Nov 7
Cc:
primiano@chromium.org
█ kraynov@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.1% regression in tracing_perftests at 492252:492253

Project Member Reported by kraynov@chromium.org, Aug 8 2017 
Reproduced locally. Culprit CL is
[1] https://chromium-review.googlesource.com/c/600860

Local results on Nexus 5X :
Before [1]
HeapProfilerPerfTest.DeduplicateStackFrames: time_to_insert= 2599 ms
After [1]
*RESULT HeapProfilerPerfTest.DeduplicateStackFrames: time_to_insert= 2691 ms
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 8 2017 

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

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


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

android-nexus7v2

Comment 3 by kraynov@chromium.org, Aug 8 2017

Cc: primiano@chromium.org
+primiano for triaging
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Aug 8 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : tracing_perftests
  Metric       : HeapProfilerPerfTest.DeduplicateStackFrames/time_to_insert


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=time.to.insert tracing_perftests

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

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


For feedback, file a bug with component Speed>Bisection

Comment 5 by benhenry@google.com, Nov 7

Status: WontFix (was: Untriaged)
This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.
►

Sign in to add a comment