I always try to keep myself using less than 4 tabs in Chromium. Used to work with several browser windows, tens of tabs each, but found out that this is just noise, and is detrimental to productivity.
Got the addon.Thanks and good luck!
Show HN: Save Memory in Google Chrome
81–90 of 298 posts
Re: Show HN: Save Memory in Google Chrome
#82For a free product, the copy on their site feels a bit more "salesy" than I'm used to for a free product
Chrome is not my primary browser, so I won't be installing this any time soon, but I thought the copy was really short and sweet, with no fluff. If this was "salesy", I wish more FOSS products were like this one.
Re: Show HN: Save Memory in Google Chrome
#83Memory use seems like a really pointless thing for users to care about. There's a widespread intuition that using RAM is inherently bad and low memory usage is a worthwhile goal, but it doesn't really make sense. The key performance goal is minimising latency, which is best served by using as much RAM as possible without having to swap out. RAM is now fantastically cheap. 16GB of DDR3 costs less than $120 in either D…
Remember not everyone can afford the latest beast of a machine that can accommodate 16GB RAM, some people still have laptops that can hold a maximum of 4GB by design limitation; it's more likely to be those people worrying about Chrome's RAM usage.
And RAM uses power, whether it's being used or not. Having more RAM means shorter battery life.
Re: Show HN: Save Memory in Google Chrome
#84Would be nice if this would be semi-integrated natively into Chrome, almost like the implementation on older Apple devices that can't have as many concurrent web pages open. On my iPad mini for example... if I am reading a few pages and switch back to another one I was looking at 30 minutes ago, it re-loads itself.
So if a tab is dormant for a while, Chrome will throw it away. Then when you recall it, the next day or whatnot, it will re-load it.
For someone who typically has a hundred tabs open at any given moment, that would be a pretty cool feature.
Re: Show HN: Save Memory in Google Chrome
#85[deleted]
Re: Show HN: Save Memory in Google Chrome
#86Memory use seems like a really pointless thing for users to care about. There's a widespread intuition that using RAM is inherently bad and low memory usage is a worthwhile goal, but it doesn't really make sense. The key performance goal is minimising latency, which is best served by using as much RAM as possible without having to swap out. RAM is now fantastically cheap. 16GB of DDR3 costs less than $120 in either D…
Not only does it save you memory, it also reduces CPU usage because Chrome would otherwise continue to run scripts in all of your open tabs.
Depending on the complexity of the web pages, having 100 open tabs can easily cripple a brand new laptop with 8GB ram.
Re: Show HN: Save Memory in Google Chrome
#87Memory use seems like a really pointless thing for users to care about. There's a widespread intuition that using RAM is inherently bad and low memory usage is a worthwhile goal, but it doesn't really make sense. The key performance goal is minimising latency, which is best served by using as much RAM as possible without having to swap out. RAM is now fantastically cheap. 16GB of DDR3 costs less than $120 in either D…
and buying a decent new machine to put that 16gb in costs some more. And migrating all your stuff over to that new machine takes time.
And then everyone will continue to write code without regards to memory usage, and we'll be complaining that Chrome 45 locks up 19g per tab, and people with your mindset will say it doesn't matter because 1TB ram chips are cheap enough at $400 to just upgrade.
Just having loads of stuff using RAM takes more time to manage. I would not have imagined in 2013 with 16G of RAM and a > 2ghz multi core processor that I would still get system hangs and beach balls in my OS, but I do.
Re: Show HN: Save Memory in Google Chrome
#88Earlier quoted context omitted.
Same error happening here along with a Butter bar stating "Manifest file is invalid." in Mac OS X 10.8.2 and Chrome 25.0.1364.160.
We've been looking at this, apparently this happens when an extension has just been released and is "propagating between servers". If the extension install is not working for you, it should start working later today once Google's webstore servers have updated
I had this issue and literally 10 seconds later I tried again and it worked fine
Re: Show HN: Save Memory in Google Chrome
#89Isn't 95% reduction claim a bit too bold? It is widely known that standard measurement of Google Chrome's memory consumption with task manager is wrong because it doesn't take data sharing between processes into consideration. How was the 95% figure produced?
He has 21 tabs opened, by reducing it to 1 tab, he has saved 20/21 lots of memory, ~~ 95% saved.
Assumptions: each tab uses same memory; no shared memory (or shared memory equally divided between all tabs), every user has around 20 tabs open given the first 2 assumptions hold true.
To me, the 95% is a magic number.
Re: Show HN: Save Memory in Google Chrome
#90I absolutely fail to see the point here. Why should I use this? Is this again one of these instances where, magically, free RAM is good? 30 tabs opened simultaneously (with AdBlock, Ghostery and Disconnect), alongside Thunderbird, Emacs (+daemon) and a full DE run up to 1.8GiB of RAM used on my machine, which is everything but fast, new, or fancy. Consequently, I still have 2GB of RAM remaining that are not directly…
"...when exactly does any computer bought at the same time (or since) have actual problems of running out of memory?"
Ah yes, I remember the days being a dev that didn't use VMs. It kinda sucked as a development environment that said: no easy way to test software on different OSes locally, no easy way to try other software which you don't necessarily trust in a confined environment (to see if it may be worth using, in which case you'd look into the trust issue more closely), etc.
If you're a dev and have "enough RAM" you're probably not trying hard enough ; )
VMs tend to use quite a lot of memory and tend to be very useful for knowledgable devs.
You asked and seemed so cocksure so these were my 2 cents...