Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have a client I do some remote server administration work for who recently started a 2-week trial period with New Relic. They have recently had some performance issues, and also asked me to take a look at things.

They saw that their memory on one of their servers was only hitting 50% according to New Relic, and became suspicious that the memory metrics / graphs were off (and emailed New Relic about it).

I spent some time this afternoon reviewing configuration files, CPU / Memory / IO graphs on New Relic, and making some recommendations.

I'm not convinced that the memory metrics are wrong. For example, on my client's DB server, New Relic said MySQL was using (at times) 3,481Mb of RAM. I ran PS to obtain the pid for MySQL, and ran the following command:

cat /proc/29313/status

Which output the following for VmRSS:

VmRSS:   3566268 kB

(which is 3,482Mb of RAM)

my.cnf has some settings I recommended that they tweak (key_buffer_size, etc...).

[Edit: If you're curious, this is irrelevant to my question below, but this particular server is running cPanel and has 32 GB of RAM. It's a dedicated MySQL server and has a number of databases running on it.]

My question is regarding whether or not VmRSS is the best metric for monitoring how much memory a certain process is using. If it is, I'm thinking about writing a script that would run on cron every 30 seconds or so for about 1-2 weeks, and then review the data. The script would look something like this:

$PID = pgrep mysql
cat /proc/$PID/status | grep VmRSS: > /var/log/my-custom-process-memory-monitor.log

Is this a good idea? Can you think of anything better? Why or why not?

share|improve this question

2 Answers 2

up vote 0 down vote accepted

RSS (resident set size) can be unreliable, because processes such as fork() do copy-on-write paging when allocating memory for the new process.

I.E if you spawn a process, give it 50M of memory to play with then fork() the loop 10 times - the RSS size will report a 500MB memory usage when in actual fact your more likely to be using just over 50M size.

For non-forking processes RSS should be generally reliable as far as I could tell.

share|improve this answer

If you still need a script, here is what i use. But as said in the previous response, know how to interpret the number

This script takes a regexp as $1 and display a number in bytes

[root@bla ~]# cat /bla/get_rss_sum_processes 
#!/bin/sh

PATH="/bin/:/usr/bin:$PATH"
export PATH

test -z "$1" && exit 0

# Does not return 0 if not found
# ps -e -o rss,args |grep -P "$1" |awk '{SUM += $1} END {print int(SUM)}'  # Prints 7.91786e+09 if too big
# ps -e -o rss,args |grep -P "$1" |awk '{print $1}' |paste -sd+ |bc
# ps -e -o rss,args |grep -P "$1" |awk '{print $1}' |perl -lne '$x += $_; END { print $x*1024; }'
ps -e -o rss,args |grep -P "$1" |perl -lne '$_ =~ s/^ *//; $x += (split(/ /))[0]; END { print $x*1024; }'
share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.