|Issue 3665||Allocation site pretenuring degrades performance in Ember|
|Starred by 17 users||Project Member Reported by u...@chromium.org, Oct 30 2014||Back to list|
v8:3664 tracks deoptimizations caused by weak references. With disabled weak references, allocation site pretenuring is the next common cause of deoptimization. "Complex List" test at http://samsaffron.github.io/ember-performance/?ember=1.8.0 runs - 185.11ms without weak references, with allocation site pretenuring (--js-flags="--noweak-embedded-objects-in-optimized-code --noweak-embedded-maps-in-optimized-code") - 169.57ms without weak references and without allocation site pretenuring (--js-flags="--noweak-embedded-objects-in-optimized-code --noweak-embedded-maps-in-optimized-code --noallocation-site-pretenuring")
Loading detail... X
Oct 30 2014,
Apr 29 2015,
Nov 14 2015,
Any progress on this?
Nov 15 2015,
Yes, months ago we tried disabling allocation site pretenuring, so that none of these deopts occur. The performance effect was negligible. Deopts occurred in those functions anyway, for other reasons.
Today (15 hours ago),
|► Sign in to add a comment|