3 ms·
Actually, there was one nugget of truth in the article, and that was the _best_ way to determine if your operating system is low on memory, is to watch it's swa
by ghshephard 17y ago
Actually, there was one nugget of truth in the article, and that was the _best_ way to determine if your operating system is low on memory, is to watch it's swapping activity. This is probably true across all operating systems, Linux, Solaris, etc..
An operating system will typically not swap out (or in) cache memory to disk, so, as long as you are exhibiting no swapping behavior, (And you have swap enabled) then you have enough memory. I think it was Adrian Cockroft, in fact, in "Sun Performance and Tuning: Sparc & Solaris" who in fact said that was _the_ way to determine if you have memory pressure on your operating system - run vmstat and watch the si and so column for activity.
- barrkel 17y agoAn OS can game that kind of statistic, though, by spending more memory on what Windows would call working set (the "hot" set of pages for a process which are preferentially kept in physical memory) at the expense of the file system cache. Also, predictive prefetching may increase paging in, but in an async fashion, so the application is never actually blocked. This may cause spurious increases in the stats. You need to examine the amount of time threads are actually blocked by the paging behaviour.