Showing posts with label Performance. Show all posts
Showing posts with label Performance. Show all posts

Monday, June 22, 2009

Firefox 3.5 and memory usage.

I came across an article while searching for news regarding firefox 3.5. I've been very excited about the new mozilla release so its been on my watch list. I stumbled upon an article from an author who decided to test each of the new browser's memory consumption. Well, i'll tell you what: I made a very bold claim in my last post that memory usage in firefox has been poor. This goes to show the world that when you make statements like these, you need to have facts to back them up with... So here are the facts:



Chrome is Yellow/orange
Opera is Green
Safari is Blue
Firefox is Red

...In a single word: huh?!

This image was publish thanks to what seems to be a very standardized test that a fellow at dotnetperls.com did. What the author did was open up the top 150 URLs (as of 19 Jun reported by alexa) into tabs of each browser using a hand made CLI. He took memory tabulations every 3 seconds for each browser, and after opening 30 tabs, closed them down to 1 tab and repeated the process with 30 new URLs. Each new URL was opened after a short random time frame (not sure why, maybe to to let pages load?).

IE8 was excluded from the test because the author couldn't open URLs in a tab directly (they appeared in a new windows instead) which is a bummer... It would be nice to see how IE8 played out to see what it brings to the table.

This test method mimics some seriously intense browsing, and its kinda realistic too... we might not open 30 tabs at once, but the concept is the same: We start with one URL, and branch from it, usually to another tab... we gather a set of tabs, and then close them down and start over. The only things that different is the time frame and the sites we look at. But this is inaccurate, becuase he uses the top 150 sites. The time thing is probably not important. I can't see memory leaking after each passing second. Another thing that different is add-ons... and this is why I'm starting to think firefox has become such a memory hog: the Add-on developers are writing bad code... But Suprisingly:

Firefox 3.5 RC2 had the lowest memory use all together.

It had the lowest max consumed, Lowest average consumed and the lowest tally at the end. Chrome ended using 3 more megs than firefox in the final tally, but peaked at 1216 megs (the system was winxp 32 with 4 gigs). Im guessing thats why chrome appears so fast as it looks to cache anything/everything... that fact that its javascript speed is a third of firefox 3.5 probably doesn't hold up so much now. The way i see it, nothing is faster than reading from ram. So if firefox is caching to the HDD, and not to memory, and chrome is caching to memory... chrome will always be quicker, at the expense of memory consumption. We can also see that firefox and chome don't "leak' over time, and both do a fantasitic job of cleaning up the memory mess.

I ended this post using firefox 3.0.11 using 80464K (78.6 megs) of memory. Im also using 15 add-ons.

Saturday, June 20, 2009

Firefox 3.5 -- Faster? Slower?

If there is one application I truly am a fanboy of, it’s Firefox. Firefox is an open source success that is changing the way people use the web. Its sole purpose is a browser that is built by people, for the people. According to GlobalStatCounter.com, almost 1 out of 3 people use Firefox, whilst 58% use IE. What’s funny is when you look at their graph, you can tell which days were work days, and which ones weren’t as people left the office browser and used the home browser. Clearly, the fox is here to stay and show the world what a browser should be.

As a former nightly [build] tester, the improvements behind the browser are monstrous. But the average Joe user is still left in the dark in my opinion, and here’s why I think so.

It’s hard for me not to form a biased opinion, because I absolutely am disgusted with Microsoft, and the entire IE line (Include IE8, which is a great improvement). I would like nothing more than the very browser Microsoft ‘shutdown’ (Netscape) come back and destroy them. Oh… Im supposed to be talking about why Firefox 3.5 sucks… ok, here I go.

One thing that really makes me angry is the slowness behind Mozilla. It’s one thing to be delayed on every single beta release, but its another when you hold up simple enhancements. Here’s one pet peeve: Auto completing Tags.

This was a feature that was added in Firefox 3.5, which started development back in September 2008? It took them that long to make these user set tags -- auto complete? Are you kidding me?! This is a massive failure on Mozilla’s part to ‘keep up’ with the stiff competition. There is absolutely NO WAY – you can say they couldn’t have made a Firefox 3.1.0 with that feature in a reasonable timeframe while they worked on other issues. It should have taken them 2 weeks to 1 month to build, test and integrate that feature and make it available. Producing software with these huge long waiting periods is not smart now. Browsers are released regularly these days almost monthly...Competition among browsers these days is at an apex. I know mozilla's tagline with brower releases is: "when its ready, we'll release it" but thats very different than: "when everything else is ready". Simply put, releasing a Firefox 3.1.0 with auto-completing seems like a very easy and quick way to 1) improve user experience immediately 2) Respond to community feedback quickly.

Another thing that really irritates me is it seems Mozilla is not listening hard enough to its users, and now it’s finally starting to bite them I think. Some of the most common complaints that users are quick to point out with Firefox is:

1) Memory usage
2) Start-up Time
3) Add-ons decrease the performance of the browser.


It just angers me that Mozilla has started to slip on things. We shouldn’t be waiting so long for quick easy enhancements. The good news is that It’s now scheduled to improve start-up time (and other internal events) on Firefox 3.6 by atleaset (greater than) 50ms, which is really a whole lot considering Safari 4 starts up in .54 secs now. Firefox 3.5 starts in 2.82 secs… If Mozilla gets smart about things (they usually do) they’ll focus on performance with add-ons… that is, adding a bunch of add-ons won’t degrade performance as much. If they can set that in motion, firefox 3.6 will be more in line of browser's like chrome 2 – easy, robust, and compatible/compliant.

I really am excited about Firefox 3.5 thou... But i think 3.6 is really going to get the users going with lightweight add-ons, themes, and an overall better browser (not browsing) experience.