Earlier quoted context omitted.
just because I had about a hundred tabs open That is a lot of tabs, though.
I average over a hundred tabs regularly. Although once the favicons disappear, I usually open a new window, or group windows by subject matter. I've tried to alter my browsing habits over the years to ease the load on my computer, but I've just come to accept that I am just one of those people. This tool is either the best thing that's ever happened, or it's about to exacerbate my problem 10 fold.
Show HN: Save Memory in Google Chrome
191–200 of 298 posts
Re: Show HN: Save Memory in Google Chrome
#192Memory 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 even in the first world there are a lot of miserly corporations that penny pinch on things like RAM.
If software that wants to target either of those markets can be made more hardware efficient, it should be.
Re: Show HN: Save Memory in Google Chrome
#193Earlier quoted context omitted.
Completely disagree. We've seen too much complacency in recent years when it comes to memory usage. Developers think it's ok for their applications to bloat out and have a huge memory footprint. I'd rather applications were developed in such a way that they were more memory efficient. I've had a recent incident in which Chrome was consuming about 7GB of memory, just because I had about a hundred tabs open! It was rea…
There's no way you could effectively work with 100 tabs open, and that is surely a smell for inefficiency. For any given task, 5 tabs is probably reaching the upper limit on what's actually _required_, with around 10 being the upper limit. Granted, you could have multiple tasks ongoing in parallel, but are you really working in parallel at that point? If not, save the tabs and return to them later. I really doubt you…
Re: Show HN: Save Memory in Google Chrome
#194Re: Show HN: Save Memory in Google Chrome
#195Earlier quoted context omitted.
Completely disagree. We've seen too much complacency in recent years when it comes to memory usage. Developers think it's ok for their applications to bloat out and have a huge memory footprint. I'd rather applications were developed in such a way that they were more memory efficient. I've had a recent incident in which Chrome was consuming about 7GB of memory, just because I had about a hundred tabs open! It was rea…
There's no way you could effectively work with 100 tabs open, and that is surely a smell for inefficiency. For any given task, 5 tabs is probably reaching the upper limit on what's actually _required_, with around 10 being the upper limit. Granted, you could have multiple tasks ongoing in parallel, but are you really working in parallel at that point? If not, save the tabs and return to them later. I really doubt you…
Re: Show HN: Save Memory in Google Chrome
#196Earlier quoted context omitted.
So do bookmarks. And this overlap becomes obvious as people inevitably ask for Chrome or OneTab to allow them to cluster tabs by topic/project -- because a linear scan is never going to 'work' for people who leave enough tabs open that it becomes a 'problem'. The underlying problem here is workflow. People are leaving tabs open as a reminder of things to which they intend to return. (Regardless of whether they will o…
Thinking on this more, the cloud-stored cache would wind up eventually being a subset of google's whole-internet-database. From which you could run a pretty awesome search service. Because it wouldn't consist of randomly spidered or submitted noise. It would only be things explicitly identified as useful or interesting . And you could rank by how many people bookmarked it, when the bookmarks happened, who they are, e…
Re: Show HN: Save Memory in Google Chrome
#197Memory 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…
i agree. this is the logic of someone willing to adapt to the environment around him. While the best solution would be more efficient programming, consumers are best served to max out their RAM and work with what they're given.
> this is the logic of someone willing to adapt to the environment around him.
How is this true? OP is saying devs should dump their app into memory and that devs need to adapt to OP's limitless RAM.Re: Show HN: Save Memory in Google Chrome
#198Earlier quoted context omitted.
tabs are not a replacement for bookmarks, the idea is not to open an ever increasing number of tabs, but rather bookmark and folder things if you need 100 concurrent research tabs. It's just the wrong way to use the browser. It would be like me arguing that driving my car with the parking brake on makes it get hot, of course it does, it's user error.
Well, no. If you've got all those tabs open and you're flitting between their contents, it's appropriate. It's not the wrong way to use the tool, it's a way to use it that's perfectly appropriate in some cases. There's no reason I should be fighting against my browser because my optimal workflow causes it to chew through memory!
Re: Show HN: Save Memory in Google Chrome
#199Earlier quoted context omitted.
if you have a 100 tabs open, you're using it wrong.
Well, if you have 100 tabs open, you might be using the wrong browser. Chrome is obviously not designed to work with that many tabs, either from a UI standpoint or, apparently, a memory use standpoint. However, I don't really see why there needs to be a strict limit on the number of tabs you can have open before your browser starts trashing all your memory. This is a problem that can be solved by designing your softw…
Maybe what we need is Chrome/FF to consider the very high tab count as a use case and handle it better, when you have so many tabs it's not easy to find the 1 in 100 that you're looking for, we would need a new find tool, possible the browser should build a client side tf/idf index and make the whole working set (workspace) searchable. You see what I mean? Until the browser changes to support this usecase, the usage will be klunky and fraught with problems.
Re: Show HN: Save Memory in Google Chrome
#200Memory 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…
Memory is cheap in the the first world. I live in Argentina, which is not a particularly poor or undeveloped country, and my 8GB of RAM are almost impressive. I know of no one who has 16 GB, and a few of my friends have 8. Most people I know of have between 1GB and 4GB, with 2GB being by far the most common configuration.
It's a bit silly, because RAM and storage seem to be the only things most people need more of on a daily basis. I suspect 5 year old CPUs would meet most people's needs just fine.