Posted Nov 17, 2011 11:09 UTC (Thu) by CChittleborough
Parent article: Huge pages, slow drives, and long delays
[T]he whole point of contemporary browsers sometimes seems to be to stress-test virtual memory management systems.
Can I submit this as a quote of the week?
This really is a classic "ha-ha-only-serious" quip. For me (and, I guess, most people) the browser is the only thing that uses large amounts of memory, so any memory-related misconfiguration shows up as browser slowdowns, freezes and crashes. (With Firefox 3 and Firefox 4, the OOM killer used to startle me once or twice a month.) Is there a good HOWTO on this topic?
to post comments)