New issue
Advanced search Search tips

Issue 776044 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 17
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug-Regression



Sign in to add a comment

14.9% regression in v8/Wasm/AngryBots/RelocSize on Atom_x64 at 48689:48689

Project Member Reported by clemensh@chromium.org, Oct 18 2017

Issue description

Performance dashboard identified a 14.9% regression in v8/Wasm/AngryBots/RelocSize on Atom_x64 at revision range 48689:48689. Graph: https://chromeperf.appspot.com/report?masters=internal.client.v8&bots=Atom_x64&tests=v8%2FWasm%2FAngryBots%2FRelocSize&checked=RelocSize%2CRelocSize_ref%2Cref&rev=48689

This is the CL where we now use 64 bit operations for the bounds check and memory accesses.
An increase of 15-16% in code size and especially reloc size is unexpected. We should investigate why this happens.

Note that this also regresses asm.js code size and probably performance (not all bots have run yet - let's see how severe the regressions for asm.js really are).
 

Comment 1 by ahaas@chromium.org, Oct 18 2017

I think especially the reloc size is surprising, because I afaict I did not change anything which effects any reloc info. The code size regression could be explained: we embed 64 bit constants now in the code instead of 32 bit constants.
Status: WontFix (was: Assigned)

Sign in to add a comment