Chrome tabs are processes with shared memory, but they're still processes. On Linux, they get kernel space mapped in. That influences their total footprint even though it's shared.
Can people just use what amounts of trifiling amounts of RAM in 2012 and stop demanding every executable be as "efficient" by an antiquated pre virtual memory metric, please?
I don't need every application to be the leanest that it can be. What I need is for every application stop assuming that 12 GB of free memory means that it's their 12 GB.
I understand the adage of free memory being wasted memory, but there's a context for that adage. E.g. if a user clicks off of a tab, the browser doesn't need to write that tab's contents to disk when 12 GB is free. A good trade off is to store the tab in memory, for X minutes. Write the tab (or more simply, the URL) to disk after those X minutes have elapsed.
Free memory isn't wasted memory though, it's file system cache memory ! If a software uses 100% of the available RAM, it means all your file system call are going to be hard drive IOs (not everybody has ssd mate).
Chrome tabs are processes with shared memory, but they're still processes. On Linux, they get kernel space mapped in. That influences their total footprint even though it's shared.
Can people just use what amounts of trifiling amounts of RAM in 2012 and stop demanding every executable be as "efficient" by an antiquated pre virtual memory metric, please?
Chrome is astonishingly good at what it does.