Death to Chrome, but idle RAM doesn't do you any favors either. Might as well cache shit there if nothing else is using it. This makes the browser more responsive, and can reduce the amount of data used by pulling something from the cache instead of downloading it all over again. What I'm more curious about is how these browsers respond when other applications are started up and request large pools of memory. Say I've got 4GB free out of 8, and I start up a game which uses 6GB. How friendly is Chrome/Firefox going to behave? Or will the OS kernel need to sic the OOM killer on them?
Death to Chrome, but idle RAM doesn't do you any favors either. Might as well cache shit there if nothing else is using it. This makes the browser more responsive, and can reduce the amount of data used by pulling something from the cache instead of downloading it all over again. What I'm more curious about is how these browsers respond when other applications are started up and request large pools of memory. Say I've got 4GB free out of 8, and I start up a game which uses 6GB. How friendly is Chrome/Firefox going to behave? Or will the OS kernel need to sic the OOM killer on them?
yea reference locality is way more important than total footprint