New issue
Advanced search Search tips

Issue 913590 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

7.7% regression in octane at 614758:614806

Project Member Reported by npm@chromium.org, Dec 10

Issue description

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

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


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

mac-10_12_laptop_low_end-perf

octane - Benchmark documentation link:
  None
Cc: ishell@chromium.org mlippautz@chromium.org
Owner: mlippautz@chromium.org
Status: Assigned (was: Untriaged)
📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/100eecd4140000

[ptr-compr] Use FullObjectSlot for off-heap slots by ishell@chromium.org
https://chromium.googlesource.com/v8/v8/+/8799f78080ee19c2ca19fff1e2ad65b0720f5c7a
Splay: 4.819e+04 → 4.95e+04 (+1315)

[heap] Improve incremental steps on allocation by mlippautz@chromium.org
https://chromium.googlesource.com/v8/v8/+/72806449de1bfcb61ebee0bdc30d9e3115413495
Splay: 4.904e+04 → 4.541e+04 (-3639)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None
Status: WontFix (was: Assigned)
Reverts some of the behavior from c32a378f4806236a10c563a1fbf576222dfd695d, so this is expected.

Sign in to add a comment