Hi Brendan,
On 01/20/2013 03:24 PM, Brendan Eich wrote:
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=12f49c4f231f&tochange=583b6c704134
Sorry if I missed a thread on this.
AWFY, has a new feature where you can zoom and unzoom[1], such as you can
blame precisely which commit was at the origin of a regression.
As Benjamin mentioned, thread-safe builds have been enabled on AWFY, the
goal was to take advantage of threaded compilation of IonMonkey. So as far
as I've heard, this slow down was "expected" in exchange of a way to check
in improvements of the compiled code.
Then there is another side-effect to it which is that using thread-safe
build also enables source compression, as it is in the browser.
I won't be surprised that the source compression is the trouble here,
knowing that the harness of sunspider / kraken is doing one load for each
run of each benchmark. One way to fix this would be to disable source
compression on sources coming from load (shell benchmark) and iframes
(browser benchmark).
[1] http://arewefastyet.com/#machine=11&about=1
--
Nicolas B. Pierron
_______________________________________________
dev-tech-js-engine-internals mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
