I'm just hoping slimming down memory usage won't go at the expense of speed... my systems have 16GB of RAM - I want Firefox to use as much memory as possible to speed up my experience. So if slimming down FF will make my disk trash more, that's the wrong direction to take.
In an age when most computers come with 4+ GB of RAM, I think people focus too much on memory. Of course there are older computers, but their OS should be using comparably less RAM. WinXP takes up 100 MB at login, so if you only have 1 GB on an older computer, you should still have no problem running modern Firefox. And if you only have 512 MB, it's probably time to upgrade since the web experience that a modern brow…
Mozilla: Are We Slim Yet?
91–100 of 101 posts
Re: Mozilla: Are We Slim Yet?
#92Earlier quoted context omitted.
nnethercote on the other hand is the "specialist" as he is in charge of the MemShrink project itself... I would trust him on this stuff.
OK, but the developers of Mozilla are specialists, too. Why not trust them? Or is nnethercote part of the Mozilla dev team? MemShrink will hopefully just be merged into the core?
MemShrink has been running since June 2011 and there have been many improvements in Firefox's memory consumption since then; these have shown up in Firefox 7, 8, 9, 10 and 11.
Re: Mozilla: Are We Slim Yet?
#93Earlier quoted context omitted.
"Writing efficient programs requires complex tricks." Says who?
I think it's more accurate to say that writing efficient program requires some modicum of thought, foresight, or planning. In a rush to put in new features for the past few years they've become the new Winamp of web browsers, stealing the crown from IE. In fact, I think from now on I'm going to refer to mozilla as winamp - until they fix their problems. I'm sensitive to the challenges facing modern browsers. But this…
As for the linking issue, that's a shortcoming in MSVC. Chrome hit the same issue earlier than Firefox did, and switched to a 64-bit linker as a result. Web browsers contain enormous amounts of code because they support enormous amounts of functionality. The code size has only a moderate bearing on the amount of memory consumed at runtime.
If you're seeing Firefox using half a GB to display a couple of static pages something is wrong. Likely causes are a busted profile or leaky add-ons.
Re: Mozilla: Are We Slim Yet?
#94I used to have loads of problems with Firefox, it was so slow... took several minutes to close, it would freeze regularly etc. I got so sick of having to clear the cache every few weeks. Then one day I noticed their hidden profile manager, created a new profile and used it instead. A few months on and everything is still working like it should. No need to clear caches, it quits within seconds, no crashes and so on. I…
Re: Mozilla: Are We Slim Yet?
#95Earlier quoted context omitted.
Yes, absolutely. These measurements in the linked article are just a complete and utter lie. Edit: The sentence above is sarcastic. Firefox has had better memory usage than its competitors for a while now, despite the belief that it is leaky.
Evidence, please.
Re: Mozilla: Are We Slim Yet?
#96Earlier quoted context omitted.
In an age when most computers come with 4+ GB of RAM, I think people focus too much on memory. Of course there are older computers, but their OS should be using comparably less RAM. WinXP takes up 100 MB at login, so if you only have 1 GB on an older computer, you should still have no problem running modern Firefox. And if you only have 512 MB, it's probably time to upgrade since the web experience that a modern brow…
I don't think Win7 alone can account for 2 GB at login, even with SuperFetch. There were probably a few programs that run on startup (antivirus, IM, OEM-specific crapware if it's a laptop, "speed launchers" like adobe reader, updaters)
Re: Mozilla: Are We Slim Yet?
#97Earlier quoted context omitted.
I think it's more accurate to say that writing efficient program requires some modicum of thought, foresight, or planning. In a rush to put in new features for the past few years they've become the new Winamp of web browsers, stealing the crown from IE. In fact, I think from now on I'm going to refer to mozilla as winamp - until they fix their problems. I'm sensitive to the challenges facing modern browsers. But this…
What problems? Memory consumption has been trending downwards for over a year now. Have you tried Firefox lately? As for the linking issue, that's a shortcoming in MSVC. Chrome hit the same issue earlier than Firefox did, and switched to a 64-bit linker as a result. Web browsers contain enormous amounts of code because they support enormous amounts of functionality. The code size has only a moderate bearing on the am…
As for busted profiles and add-ons, I don't know what to say to that that's not blatantly offensive, so I'll just offend. Winamp is a fat, ugly, smelly cow. It didn't used to be. Either the web is now a pig-farm, and everybody is writing javascriptish-do-nothing-scripts that allocate hundreds of megs without purpose (in which case, winamp needs to take a leadership role in fixing the javascript problem), or winamp has other serious issues it needs to address.
Either way, it's not my problem. Winamp devs can deal with that stuff.
Re: Mozilla: Are We Slim Yet?
#98I'll admit that I was expecting a site more like http://hasthelhcdestroyedtheearth.com . It's really nice to see that Mozilla is still taking this stuff into consideration. After all, memory has been a point of contention in the community since Firefox 3 or so. I know the FF detractors are going to come out of the woodwork at any moment, but I feel that reports of Mozilla's death have been greatly exaggerated.
Do you use it as your fulltime browser? Why is it better than Webkit-powered alternatives?
Re: Mozilla: Are We Slim Yet?
#99The problem is that you have some stubborn devs or decisions that were made a long time ago that need to be reversed but for whatever reason are not being reversed or are hard to change.
What I care about is perceived start up time and perceived overall performance.
For perceived start up time to improve they have to stop doing some things that they normally wait to finish doing before showing the screen. Like waiting for all of the tabs to load, checking for updates to add-ons, etc.
For overall performance to improve I think they need an extra performance mode that will restrict what Addons can do.
Re: Mozilla: Are We Slim Yet?
#100They are measuring and trying to fix the wrong things. I don't care if you think you are 'lean'. The problem is that you have some stubborn devs or decisions that were made a long time ago that need to be reversed but for whatever reason are not being reversed or are hard to change. What I care about is perceived start up time and perceived overall performance. For perceived start up time to improve they have to stop…