undefined | Better HN

0 pointsslacka13y ago0 comments

To set the cache to only 100MB, you can always use the "--disk-cache-size=104857600" flag.

My issue with chrome is that it eats up a lot more RAM than Firefox. When doing research, I often have 30-50 tabs open. With Chrome my system runs out of physical RAM and starts thrashing. With Firefox, the UI becomes unresponsive due to it's single threaded design.

I wish Chrome would start a Memshrink project like Mozilla did or Mozilla would finish with they started with electrolysis.

0 comments

6 comments · 3 top-level

Cthulhu_13y ago· 3 in thread

> My issue with chrome is that it eats up a lot more RAM than Firefox. When doing research, I often have 30-50 tabs open. With Chrome my system runs out of physical RAM and starts thrashing. With Firefox, the UI becomes unresponsive due to it's single threaded design.

Alternatively, since you seem to be a power user, you could consider upgrading your hardware to 8 or 16 GB of memory; it's not that expensive nowadays, and given your power user status, more memory = faster computer experience = higher productivity. Or just more tabs.

[old man mode] Back in the day we upgraded our computers instead of blaming software.

emn1313y ago

There's no need to answer FUD with FUD: Firefox's UI does not become unresponsive with increasing number of tabs. Certainly not with just 50 anyhow; I do that all the time and never notice a slowdown. The tab-closing animation is less smooth than chrome's however. And while it's certainly true chrome uses more memory per tab, I can't imagine running into that problem very easily even on somewhat outdated hardware. A 4GB system should be able to do 50 tabs normally, and how much more do you need?

slackaOP13y ago

I have a quad-core, 8GB machine at work and a dual-core 4GB machine at home. Both are running Win7 64-bit. How much more do I need?

I have noticed slowdown in Firefox's UI on both machines. More important than number of tabs, is CPU usage. For example my HTML5 heavy trading platform often causes the single-threaded Firefox UI to freeze and slowdown on both machines, while I have never noticed Chrome freezing when this site is open.

On the other hand, Chrome's UI runs smooth as butter until either open tabs or other programs bring memory usage to over 90% Physical Memory in the task manger. Recent builds hit that wall a lot quicker than it did a year or so ago.

ksec13y ago

I am a Firefox users so this is not coming from a bashing Firefox POV. I could open 100 - 200 Tabs in Firefox without problem if i disable Javascript and all Add on.

As soon as you have some heavy JS usage website, even 50 Tabs can slow down the UI. This is on Quad Core Ivy and 8GB Ram with SSD.

The amount of JS on one website now is getting insane. Chrome have similar problem as well like the OP have said. Just a different one.

So it is not FUD at all.

1 more reply

thelukester13y ago

On my 2GB netbook, chrome has gone from my preferred browser to unusable due to the high memory footprint of recent builds. One killer is the GPU process often taking 200+MB.

Before giving up, and switching to FF, I tried the --disable-gpu --disable-software-rasterizer switches to disable the GPU process but that prevented videos from playing at full speed.

lucian190013y ago

A large part of Chrome's memory usage is due to its process isolation. It's also what makes it more likely to be responsive, even with UI blocking bugs.

j / k navigate · click thread line to collapse