SpiderMonkey never terminates on JS fannkuch benchmark
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
People
(Reporter: lth, Unassigned)
References
Details
(Keywords: regression)
(Spun off from bug 1532279)
Clone https://github.com/lars-t-hansen/rust-fannkuch-js-and-wasm. Edit js-benchmark.js and replace print with console.log. Run node js-benchmark.js and observe that it terminates in a reasonable about of time (2-3s). Now run it in spidermonkey and observe that it does not terminate at all. (Release build off of last Friday's mozilla-central.)
I tried various combinations of switches to trigger different parts of the execution pipeline, and nothing seems to help - my patience runs out before it terminates.
In the past (see above bug), running time on SpiderMonkey has been 2-5s.
|
Reporter | |
Updated•4 years ago
|
|
||
Comment 1•4 years ago
|
||
That's odd. It works fine for me; on my desktop, using the latest m-c, it takes a little over 5 seconds:
0:00.41 /home/iain/src/central/obj-opt/dist/bin/js /home/iain/src/js-benchmark.js
556355,51
Time: 5500
(For comparison, node takes ~2.7s on this machine, so we're not great, but we're not completely broken.)
Are you sure you were running a release build? My debug build took almost a minute to run fannkuch(10), and it appears to scale exponentially, so it wouldn't surprise me if a debug build running fannkuch(11) didn't terminate in any reasonable timeframe.
|
|
Reporter | |
Comment 2•4 years ago
|
||
Tested again now, and it does terminate (6.5s, almost 3x that of wasm and node). Searching back in my history I see I accidentally used a release-debug build last time :-(
Description
•