Monitor users RAM usage?

We monitor RAM usage like that. The simplest way to know that swapping is happening is to look at the total number of pageouts in a given period of time.

If you look at the output or vm_stat, you'll see the total pageouts since the last boot.

If you just want something to trigger when any pageouts happen, just get that number every few minutes, and if it goes up from the last time, take some action.

If you keep a history of that number every few minutes, you can use the data to find times when it increases rapidly, and perhaps isolate patterns of memory over-use.

The historical data can be very useful when a user calls up saying "I need more RAM" :-)

-Chris

This may be of some help...

#!/bin/sh
pageIns=`/usr/bin/vm_stat | /usr/bin/grep -i pageins | /usr/bin/awk '{print $NF}' | /usr/bin/sed 's/.//'`
pageIns="<page_ins>$pageIns</page_ins>"
pageOuts=`/usr/bin/vm_stat | /usr/bin/grep -i pageouts | /usr/bin/awk '{print $NF}' | /usr/bin/sed 's/.//'`
pageOuts="<page_outs>$pageOuts</page_outs>"
echo "<result><stats>$pageIns$pageOuts</stats></result>"

Fantastic! What do you use as a benchmark for pageouts/timeframe and what method do you use to monitor that? I was thinking about writing an EA to track it but havent decided on where to store the counts... I'd be really interested to see what you're doing if you don't mind sharing?

Thank you both! I'm trying that script out now.

Here's basically what we do - its part of a much larger data-gathering script that runs every 10 minutes. The data eventually ends up in a central database (currently not the JSS, but I'm working slowly on getting it integrated :-)

#!/bin/bash

# where to remember the data for next time
LAST_POUT_FILE=/var/log/last_pageout_check

# timestamp of the last boot
LAST_BOOT=`sysctl -n  kern.boottime | sed -E 's/^.*sec = (.*),.*/1/'`

# when are we?
NOW=`date +%s`

# here's the number of pageouts since boottime
CURR_POUTS=`vm_stat | grep -i pageouts | sed -E 's/[^[:digit:]]*([[:digit:]]+).*/1/'`

# if the last pageout file exists and is newer than the last reboot
if [ -f "$LAST_POUT_FILE" ] && [ `stat -f '%m' "$LAST_POUT_FILE"` -gt $LAST_BOOT ] ; then

    # use the file and note the interval (in seconds) since it was recorded
    LAST_POUTS=$( < "$LAST_POUT_FILE" ) 
    POUTS_INTERVAL=$(( $NOW - `stat -f '%m' "$LAST_POUT_FILE"` ))

else
    # otherwise, the last count is zero, and the interval is seconds since bootime
    LAST_POUTS=0 
    POUTS_INTERVAL=$(( $NOW - $LAST_BOOT ))

fi 

# remember the number of current ones
echo $CURR_POUTS > "$LAST_POUT_FILE"

# the number of pageouts that happened during the interval
RECENT_POUTS=$(( $CURR_POUTS - $LAST_POUTS ))

# output comma-delimited data
echo "$NOW,$RECENT_POUTS,$POUTS_INTERVAL"

I've slightly modified 'jhbush's script to display only the pageout count as an EA

#!/bin/sh
pageOuts=/usr/bin/vm_stat | /usr/bin/grep -i pageouts | /usr/bin/awk '{print $NF}' | /usr/bin/sed 's/.//'
pageOuts="$pageOuts"
echo "<result>$pageOuts</result>"

However, I'm really interested in the script ChrisL has submitted here. I'm going to start playing around with that to see if I can't get it worked around as an EA. I just have to decide on the metric. This is some great info!

For anyone currently tracking pageouts... how do you measure frequency? By this I mean, Do you compile daily page out stats in a larger database? Do you average daily pageouts? I'd like to write up something as an EA, but am spending a lot of time trying to figure out how I'd like to measure this effectively. Thanks for all the help so far!

Had my email notification off... in any event, this is pretty much how I figured that it would go. Thanks!

Hey, reviving this old thread… I started collecting the pageouts with the script above, but I really don't know at what point we could consider that the device is "using too much RAM" or what level of pageouts is acceptable.

Could you provide any hints on this?

Thanks!

In our case we use high pageout over time numebrs as an indicator that we should at least talk to the user about their experience to make sure we have them in the proepr device. Also, given that we're MacBook Air/Pro heavy we have increased the RAM in the machines we're buying across the board. Ups the resale value quite a bit as well.

In reality, we find the users who have 30+ tabs open on three different browsers.