Chrome gobbles up RAM and makes other programs run slower, while Firefox in its newer incarnations is the ideal socialist citizen, sacrificing browsing experience for the performance of other programs.
I then remembered that Privoxy is a local proxy server used to filter ads & web pages in general, & it could be used as a local proxy with the authentication added for the main proxy. However, while looking at the Privoxy page on wikipedia, I came across another program called Proxomitron (the developer has unfortunately passed away, but the program lives on) that does pretty much the same thing & is primarily GUI driven (Privoxy has quite a few config files with a frontend, but not as simple to use).
So, here’s a step by step guide to setup Proxomitron as a local proxy to take care of the proxy authentication problem faced by many programs:
1) Start Proxomitron and uncheck the filters (you could leave them checked if you want to use the filtering capabilities, but that adds an overhead to your system) & check the “Use remote proxy” option
2) Click the “Proxy” button to configure your internet proxy server (format – <proxyname>:<port>) and right click on the text field to bring up the advanced proxy settings menu
3) In the advanced proxy settings, enter your username & password for the authenticated proxy & you’re done with the setup
4) Open the “Internet Options” in IE & put in localhost as your proxy & port number as 8080 (unless you’ve changed it)
That’s it and you should now be able to use the programs that make use of the IE proxy settings to connect to the internet. In case any program has its own proxy settings without an option for entering the proxy authentication, just use the same settings as in step 4 & it should work. In fact, you can also use this setup for your iPod Touch/iPhone – you’ll just have to replace the “localhost” address with the IP of your computer, and of course have them both on the same network – to make your net connected Apps work.
Is Prism really an evolutionary step?
I ran the benchmark once each on the browsers. My system configuration is as follows:
- Pentium 4 2.8 GHz
- 2 GB RAM
- Windows XP Professional with SP2
Do note that I did not create any special setup for the browsers, i.e., they had their plugins and extensions enabled. This might have affected the performance, but then again it also simulates more of a real world scenario.
Results (links lead to results on SunSpider page – complete results in this Google spreadsheet)
|Browser||Time (ms) – lower is better||% better than FF2|
The benchmark result shows that there have indeed been significant improvements in Firefox 3 over 2, with an overall gain of over 50%, and the performance is close to that of Opera. There are tests where Firefox trumps Opera, but overall Opera still has the lead. However, there seems to be some downsides to the Firefox 3 optimizations at least as of beta 2, as the rich interfaces of Yahoo Mail and Windows Live Mail do not work.
The other important observation is that Flock is significantly faster than Firefox despite being based on the Firefox 2 code. The Flock developers have definitely optimised the code, and this shows. (Update: not sure about this, based on Mike Shaver’s comment below, and my own observations on a different PC)
As for IE7, it actually performs reasonably well, and is on par with or better than Firefox for a majority of the tests (also shown by Jeff Atwood). However, the string tests turns out to be IE7’s Achilles heel with the time taken (72347.8 ms) being 10-15x that of the other browsers.
I haven’t tried out the benchmark on Opera 9.5 (still in beta) yet, and there may be further optimizations there too. Safari was also pretty fast as per Jeff Atwood’s post. I hope to test out these two browsers as well, and possibly on other systems to see how much the system configuration affects the results.
Check out the detailed results in this Google spreadsheet (Firefox 3 seems to have problems with Google Docs – it was only showing the all documents page).
Update: Based on Mike Shaver’s suggestion (comment no.1) I tried out the tests for Firefox 2 and Flock on a different PC (Athlon 64 3200+, 1 GB RAM), both in safe mode and with extensions enabled, and found the results to be similar (FF2 is slightly faster this time). I hope to do more tests, and in the mean time if you have any results or observations to share you are welcome to share them.
|Browser||Time (ms) – lower is better|
|Firefox 126.96.36.199 w/ extensions||
|Firefox 188.8.131.52 safe mode||
|Flock 1.0.3 w/ extensions||
|Flock 1.0.3 safe mode||
I had posted earlier on my initial experiences with the Firefox 3 beta inside a sandbox, and decided to hold off on a full time switch to the beta as most of my favourite extensions were incompatible. The incompatibility status for the extensions has not changed, but I discovered an easy workaround (no hacking around xpi) today when looking around for a working mousse gestures extension.
All I had to do was to create a “extensions.checkCompatibility” boolean field in the Firefox about:config and set it to false. As you can guess, this disables the compatibility check for the extensions, and all the disabled incompatible extensions are enabled (with warning messages). Of course, this does not guarantee that the extension will work. Also the browser crashed on the first restart (the subsequent restart was fine though).
However, I was able to get most of the required extensions working this way (not extensively tested). They include Mouse Gestures, del.icio.us bookmarks, Greasemonkey (Update 22/01/2008: Greasemonkey just got an update today and is now supported on Firefox 3 beta), MR Tech Local Install (this one can override extension compatibility versions) and PDF download. Some extensions remain unusable though like Tab Mix Plus (possibly due to the architectural changes) and Google Gears (might be because I’m running inside a sandbox). Not a major loss, though I miss some of the tab tweaks provided by Tab Mix Plus.
I plan to use the beta inside the sandbox as my primary browser now that the extensions problems has been worked around. I’ll post my findings in in a few weeks, by which time some updates are likely to be available.
As for the changes from beta 1 to 2, check out the release notes. Of note is the fact that the rich interfaces of Yahoo Mail and Windows Live Mail are still unsupported.
There seem to be further tweaks to the memory usage (image below) and rendering. The interface hasn’t changed much, though a Smart Bookmarks folder seems to have been added to the bookmarks toolbar. The earlier location bar update that includes suggests autocomplete entries based on the page titles and not just the link text is quite a useful feature.
And to sign off here’s a comparison of the memory usage of v2 (top – gray) vs v3b2 (bottom – blue) with the same 8 tabs open in each, taken using process explorer. Note that there are fewer extensions in v3b2 and it is running in a sandbox.
The Firefox 3 Beta 1 (download) was finally launched this week, and from what I’ve been reading, it promises better memory usage along with interface tweaks. So, I decided to give it a spin. There were some basic concerns of course, like conflicts with my existing Firefox 2 setup, incompatible extensions and general instability/performance issues.
However, there’s also an easy way to overcome this problem using sandboxing software like Sandboxie and Altiris SVS (lifehacker article on using SVS). I had installed Sandboxie sometime back after reading about it in a few places. It is quite simple to use – you just need to launch the desired program using the Sandboxie tool. I went ahead and got the Firefox 3 beta and ran the installer in the sandbox. The thing to note about the sandboxing is that though the installation is in a sandbox, the Firefox settings (including extensions) from my version 2 installation would be used, but in a read-only fashion, so that compatible extensions can be used as on a regular upgrade, bookmarks are carried over, and so is the session restoring.
Anyway, the beta installed without any glitches. Then, on launching the browser, it notified me of a bunch of incompatible extensions (as suspected) – greasemonkey, mouse gestures, del.icio.us bookmarks, downthemall, tab mix plus to name a few. So much for hoping to use Firefox 3 beta as a version 2 replacement.
The interface tweaks were seemingly minor, but did make a difference. For one thing the toolbar paddings seems to have been reduced, which gives it a cleaner look. Then there’s the star in the address bar for quickly marking sites along with the places folder in the bookmarks toolbar which lists the recently and frequently accessed sites, tags etc. The bookmarking process has also been overhauled, with support for tags along with with a modified organizing interface. All in all, the interface tweaks are quite nice, without any drastic changes.
Coming to the performance, the memory usage did seem to be lower than version 2, especially after leaving it running for some time. In version 2, the memory usage gradually increases with time and number of opened tabs. This aspect seems to be a lot more efficient in version 3, in the beta itself. The interface also seemed snappier when switching between tabs, and opening new ones. Of course part of this could also be due to the fact that almost a dozen extensions were disabled in the beta due to incompatibilities. But, it seems we have something to look forward to on this front.
I have been seriously considering the switch to Flock (which is based on Firefox 2, and is compatible with many of the Firefox extensions) for the last few weeks after being bogged down by the version 2 performance. Firefox 3 seems to hold some hope on the performance front in addition to other improvements, and should be a welcome upgrade from version 2. However, I won’t be switching till the extension compatibilities are sorted out (if not for the extensions, I would’ve been on Opera). What about you?
The data: URI (RFC 2397) allows the inclusion of small data items like images, text etc inline. It is quite useful for embedding small bits of data into scripts, as no external source needs to be referenced. In fact, I had come across the data: URI through a Greasemonkey script named Smilize which substitutes the usual smiley texts with images (embedded in the script using the data: URI).
There are a few sites which convert small images, html etc to the data URIs. There is one major drawback with the usage of the data: URI – it is not supported in Internet Explorer. So, for the time being its utility is mostly restricted to Greasemonkey and Opera scripts, till IE support is available (maybe in version 8?).
P.S.: I came across a new addon for IE 7 – IE7Pro – which provides userscripting functionality plus some other features like Ad blocker, mouse gestures etc.
The blog post » Can we STOP with the sensational browser flaw reporting? Please!
gives a pretty good indicator of the way the relatively minor flaws in
the latest Internet Explorer 7 & Firefox 2.0 browsers are being
blown out of proportion. In fact, as per the links given by the author,
the older versions of the browsers have had several critical flaws
being reported, and these have pretty much gone by unnoticed.
I will be providing information on a number of Firefox plugins in this post in due course. First of all let me list out the extensions I plan to cover, along with a one line description:
- Adblock* – block ADs
- Flashgot* – use download managers with Firefox
- Fasterfox* – tweaks to speed up browsing
- CustomizeGoogle* – removes ADs
Update: Something seems to have gone wrong, & most of the content that I had added to this post, including the reviews, seems to have disappeared. I will be rewriting the reviews in due course.
Strictly speaking, Maxthon may not be a browser by itself as it uses the Internet Explorer engine. However, for the people who are using IE as the primary browser, it is a very feasible alternative. It is probably both good & bad as it uses the IE engine, depending on one’s point of view. It can be looked upon as a pretty good replacement for IE itself, atleast till IE7 is released. Continue reading