5 ms·
Not really, especially if you're doing a lot of research, or for whatever reason the page is particularly complex and it causes the process that tab is running
by kintamanimatt 14y ago
Not really, especially if you're doing a lot of research, or for whatever reason the page is particularly complex and it causes the process that tab is running under to consume a lot of memory.
- DavidHogue 14y agoI end up with quite a few tabs open myself. I find if I bookmark a tab, add it to Pocket, or copy the URL into my notes that I'm far more likely to go back and actually read it. Before I would keep tabs open for weeks "just in case".
- chenster 14y agoI can relate, I do the same to keep the tabs open so to read them later. Most of them end of not reading them weeks later. Never use Pocket. Presumably, it's similar to ReadItLater or Instapaper? Perhaps indeed that's better approach.
- adventured 14y agoNo, a hundred tabs is still far beyond a lot. If a hundred tabs is not really a lot, what would be? 250? 1,000?
- kintamanimatt 14y agoWhatever the brightline test for "a lot" is, there's no compelling reason each tab should be consuming about 70MB. Under Chrome, each tab runs in its own process, which is certainly a contributing factor. I appreciate this is for stability and security, but it's not the best solution for the problem and has some serious drawbacks, i.e. horrible memory usage.
- ibrahima 14y agoAs I said in another reply to one of your comments, I don't think 70MB is a lot per tab. I'm fairly certain that if you run Firefox 2 for instance it'll use close to that amount for one tab.
- kcbanner 14y agoThe fact that it is its own process is a very small contributor to per-tab memory usage.
- hnriot 14y agotabs 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.
- kintamanimatt 14y agoWell, 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!
- hnriot 14y agono. when number of open tabs < 10-20, yes sure, but when that number reaches 100, your doing it all wrong. Its not about how much memory it consumes, that's irrelevant, if you need more memory just go to crucial.com, it's dirt cheap. Its about using the tools properly.
- kintamanimatt 14y agoI can't argue the position for this workflow better than I already have. I refute the idea that I'm "doing it all wrong". No, I'm not and this was the only efficient way to get what I needed to do done. My laptop's motherboard can't handle more than 8GB, so I don't even have the option of putting more RAM in it as it already has 8GB. Also, I shouldn't have to keep throwing in memory to handle applications whose coders feel it is fine and dandy to gobble memory with reckless abandon. Why should I bear the financial cost of a poorly designed application? I'm most certainly using my tools properly whether you agree or not. I'm not bitching about 5,000 tabs causing excessive memory usage, I'm complaining about 100 which is not that many during research that requires going from page to page, or opening lots of links without having to remember where I was at in each part of my stack; I've got less working memory than my computer!