I took an action item from the Hotplug SIG meeting a while back to check whether or not sar records any memory statistics that might change during a memory add transition (implying we need to check that it works, and regression test it). Here is an example of one option I just ran on my laptop. maryedie@maryedie:~> sar -r 2 2 Linux 2.6.13-15.8-default (maryedie) 04/25/2006 04:41:43 PM kbmemfree kbmemused %memused kbbuffers kbcached kbswpfree kbswpused %swpused kbswpcad 04:41:45 PM 17300 758280 97.77 22032 325236 917492 131324 12.52 21840 04:41:47 PM 17316 758264 97.77 22040 325236 917492 131324 12.52 21840 Average: 17308 758272 97.77 22036 325236 917492 131324 12.52 21840 Of these, I believe these stats need sar to be aware throughout its execution of the total amount of memory on the system (not just when it initializes): kbmemfree: Amount of free memory available in kilobytes. %memused: Percentage of used memory. The other stats (and others provided by other options like -R ) would likely change as a result of the use of memory, but that would be as an indirect result of the transition. _______________________________________________ Mary Edie Meredith Initiative Manager Open Source Development Labs maryedie@xxxxxxxx 503-906-1942
