Skip to content

Tag: Feedly

Is your computer slow? Maybe it’s your browser’s fault

I revived one of my old computers recently. Not a very old computer – built-in 2007, with a Quad Core Intel QX9650, 2GB RAM, 500GB – 7200 RPM SATA HD. After installing on it a freshly minted Win8.1 and some other stuff, it was ready to go.

When I’m at my computer, I always have a Chrome window open, with Gmail, Calendar and Feedly, and other stuff that I am currently reading. Outlook is usually open (for work email), Google drive is on, and that is mostly it. But my computer was very, VERY slow! I decided to investigate some more, closed everything and started opening things one by one. Since my RAM is “relatively” low, I guessed this was the problem, and what I found was very interesting, reminding me of a post I did some time ago.

My initial Chrome configuration, with all the plugins I use (Zemanta, Buffer, and others) consisted of 12 processes, consuming in total 235MB RAM. No only that, but the memory consumption was changing all the time, which probably caused many page faults – I deduce this by the amount of sound coming from my HD. I decided to do a simple comparison between browsers – Firefox, IE, and Chrome, to see if by changing browsers my experience would get any better. To set the same baseline, I also disconnected Chrome from my Google account, and removed all extensions. The results are pretty interesting. Each row shows the amount of memory (MB) consumed by each browser in the scenarios I tested, and the number of processes that the browser spawned (in parenthesis):

Browser Initial CNN SO Facebook GMail
Inprivate IE 12 (2) 151.2 (2) 46.8 (3) 110.7 (3) 255.7 (3)
Incognito Chrome 10 (2) 196.5 (4) 71 (3) 109.9 (4) 229 (4)
Private Firefox 52 (1) 119.3 (1) 67.4 (1) 137.8 (1) 182.8

From a memory consumption perspective, there is no much difference. While Firefox start with large memory, when one page is viewed, this doesn’t matter much. What is more interesting here is that while Firefox works as one process, both IE and Chrome use multiple processes. I have seen chrome spawn more than 10-15 processes when I do some hard browsing.

But from the usability perspective, since I switched to Firefox, my HD has stopped making noises all the time. What I presume is happening is that the IPC (Inter-Process Communication) creates many page faults that go to the disk (because I have relatively low memory), and slow down things. This is applicable both for IE and Chrome.

So starting now, I am using Firefox for all my browsing, to see how it goes. Will keep updating this post as I add more workload to see if the performance is really better. Just for starters, I now have 13 open tabs, including GMail. Firefox takes about 290MB RAM, but only one process.

Update 17/12/2013: after 3 days running Firefox on my desktop, having 11 open tabs with Gmail, Google Calendar, WordPress and other stuff, memory consumption is now 563.6MB!!!