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

I've been analyzing my munin graphs and found that my server's memory usage is quite high.

Question:

Is my server memory usage too high? If it is should I:

  • get a larger EC2 instance with more memory
  • change some configurations (suggestions?)

Background:

  • EC2 Large Instance
  • Over the period of one year I made a couple of minor changes to the server. I however don't remember all the changes I've done.
  • One change was enabling MySQL caching. It's easy to see this in the graph attached below.
  • As far as the PHP/backend for our web application there wasn't many changes done.

Attached Stats:

Side Note:

I'm a pretty good developer (PHP...) but when it comes to linux I'm slowly learning. This question might be a bit general. I'm hoping for a general guidance so that I can learn and once I learn I can post a more specific question.

share|improve this question

closed as not constructive by womble, Ward, HopelessN00b, Scott Pack, voretaq7 Aug 27 '12 at 3:23

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

1 Answer 1

up vote 3 down vote accepted

Your memory usage is perfectly fine.

The vast majority is "cache", which is a very good thing. The Linux kernel (well, most OS' actually) will cache data in memory so that subsequent requests for the data come from memory rather than needing to be fetched from disk. Fetching data from memory is massively faster than fetching from disk.

Other things to look at are:

  • swap: Its not unusual to see some swap used on a typical system. The important thing is that the server isn't swapping a lot. Munin's "Swap in/out" graph can shed some light, but in your case swap usage is constantly 0, so there's no issue.
  • committed memory: this should typically be less than the total physical RAM available to the server. If it's higher, you start running the risk that the kernel needs to start using swap, aka disk paging, which is bad as I said previously.

See also: http://www.linuxatemyram.com/

share|improve this answer
    
Amazing! Thanks for the link. –  iDev247 Aug 4 '12 at 22:16

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