Re:64-bit Firefox for Windows should be prioritized, not sus...
by Symmetry on Tuesday November 27, 2012 @09:16AM
(#4837179)
It might be that it's simply Firefox's JavaScript interpreter which hasn't been optimized for 64-bits. As far as I know other JavaScript interpreters don't suffer from this problem, and with LuaJIT, which should be fairly similar to a JavaScript JIT compiler, at least I have the numbers to back it up: http://luajit.org/performance_x86.html
[ Parent
| on HN ]
Re:64-bit Firefox for Windows should be prioritized, not sus...
by nuje on Tuesday November 27, 2012 @09:23AM
(#4837207)
Those LuaJIT numbers are really microbenchmarks with small working sets though, and wouldn't show the cache effects of increased memory usage.
Re:64-bit Firefox for Windows should be prioritized, not sus...
by Dylan16807 on Tuesday November 27, 2012 @01:59PM
(#4838198)
LuaJIT doesn't have increased memory usage. 32 or 64 bit, it always packs pointers into the low bits of NaN doubles. Addresses fit because current 64 bit chips actually use 48 bit addresses.
(LuaJIT also uses a limited memory arena for allocations but it's not inherent to the design; it could be changed but the current garbage collector can't handle that much data)