5 ms·
Suspended != Abandoned Sometimes it saves a huge amount of effort to wait for things to mature otherwise before proceeding. If your firefox is using more than
by ck2 14y ago
Suspended != Abandoned
Sometimes it saves a huge amount of effort to wait for things to mature otherwise before proceeding.
If your firefox is using more than 4gb of memory ( >2gb via LARGEADDRESSAWARE) you have other problems, and 32bit code is almost always faster than 64bit with current CPUs.
- rplnt 14y ago> Suspended != Abandoned Well, the original quote said that it won't "ever see the light of day".
- hackmiester 14y agoI fail to see how if "my Firefox" is using a certain amount of RAM, I have any problem at all. If I am using Firefox in a reasonable way (i.e., not 400 tabs open or something), why should my RAM usage even be a function of anything I am doing, at least to the point for it to utilize 4GB of RAM?
- konstruktor 14y agoI certainly hope that memory is a function of how much content is loaded because one would expect a modern desktop application to keep all its non-persistent working data in memory, and not try to outsmart the OS when it comes to memory management. After all, RAM is cheap, your OS is perfectly capable of managing virtual memory, and addressable memory isn't a problem on 64 bit systems. The irony is that one of the reasons why modern mobile OS often feel faster than desktop applications on much faster hardware is because their APIs force programmers to give up this kind of hubris. So basically, Mozilla is building FirefoxOS, which will enforce the reasonable behavior they aren't capable of themselves when in the role of an application developer.
- hackmiester 14y agoI think RAM usage should be a function of work load. However, here I sit with 12 tabs open and Firefox using almost 1GB of RAM. I don't know when this became okay, but I could see Firefox using 4GB of RAM, easy. At this rate, that would be due to the ungodly workload of 48 tabs.
- CamperBob2 14y agoNo, 32-bit code is not faster with current CPUs. x86 apps are more register-starved than they are cache-bound. I don't know who started this urban myth about x64 applications somehow being slower than equivalent ones running under WoW64, but it needs to either be backed up with specifics -- what apps are slower, and why? -- or stop being propagated. (Source: extensive firsthand experience with performance-sensitive C/C++ development for Windows.)
- kevingadd 14y ago64-bit Firefox is slower for some workloads because the JavaScript heap is dramatically larger (Due to the doubled pointer size). As it happens, large portions of Firefox are written in JavaScript... I'm sure there are some use cases where it's faster, of course, but having your heap be 50-100% larger (yes, really that much, I've measured it) is pretty hard to overcome just by adding a few extra registers. I expect this is why Java has support for using 32-bit object pointers in 64-bit mode. Features like that would probably help Firefox tremendously.
- stephencanon 14y agoHeap growth moving from 32b to 64b is rarely on the order of 50-100% larger. 20-30% is much more common (100% would imply that your application stores no actual data, only pointers and sizes; I know that pointer-chasing is very much in style these days, but that's ridiculous. Even the 1:1 ratio implied by a 50% figure is an extreme outlier). Further, raw heap size typically has marginal impact on performance; locality of reference and size of working set are far more important. It doesn't matter if your raw heap usage grows by 30% if the majority of your accesses are to the same working set of data either way. At the same time, a well-crafted interpreter or JIT (which people seem to think is important in browsers) benefits heavily from increasing the size of the register set. Even in more typical use cases, even without aggressive optimization, speedups of 10-20% are common in moving from x86 to x86_64.
- kevingadd 14y agoYou can tell me what your think the behavior is actually like, but I can point you to a HTML5 game that uses 50-100% more JS heap and runs slower in 64-bit builds of Firefox :) You say a larger heap has marginal impact on performance and that locality and working set size are what matter. If larger pointers make the heap bigger, then the working set is going to grow as well, and locality will be worse because the larger pointers mean less objects fit into a cache line.