About graphs and memory usage, am i looking at the graphics wrong?

Posted on January 8, 2017

Hello, i hope you guys could help me with an issue. I just installed a fresh WordPress(one click) on the smaller droplet(5 dollars). But i have a worry.

-When I look at my memory usage into Droplet managing, at the first right graphic is stable(always under 100%) but when going to the last graphic(bottom right), apache2 process is running at 99% of Memory(one time was over 100%), is that normal?.

Htop show me memory usage is always under 400mb.

-What would mean that 100%+ graphic if physical memory never shows more that 70% of usage? is this normal?

over 100% apache2: http://imgur.com/a/qHMrY actual 95% apache2: http://imgur.com/a/Dc5P4

Also, the WordPress is already protected against XML-RCP and slighly optimized.

Thank you very much, Gabriel

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Jonathan Tittle

January 8, 2017

Accepted Answer

@geramirez

When you deploy a fresh droplet, since the droplet has to deploy the image, start all the processes and services, and do backend work, the CPU & RAM is going to shoot up; that’s normal. Normally the accuracy of the graphs normalizes after a week or so (i.e. when there’s enough data to really gauge performance).

That said, the CPU & RAM of your droplet will play a role as well. If you’re running a 512MB Droplet, CPU & RAM will fluctuate depending on traffic and the what the plugins you’ve installed are currently doing when each page is loaded more than would be the case on say, a 1GB or 2GB droplet.

When it comes to performance, there’s only so much you can do on the frontend (i.e. with plugins). Caching is a big one and that’s going to be what provides you with the best overall performance boost without having to dig in to the server.

Beyond that and you’re going to need to dig in to performance tweaking.

If you don’t plan on running this on multiple servers, using PHP’s OpCode Caching is probably going to provide the best overall performance increase. If you do plan on spanning to multiple servers, then I’d recommend going with Redis or Memcached (I prefer Redis).