Twice today my server memory usage has climbed from its stable 35% upto 92%. The first instance corrected itself, the second time I power cycled the droplet. How can I determine which process is hogging all this memory?
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.
Click below to sign up and get $200 of credit to try our products over 60 days!
You can ssh to your droplet and use either
htopto see which processes is consuming most of the droplet’s memory. In order to see the memory usage in htop, once you’ve executed the htop command use Shift + M or just click the MEM% sign with the mouse (htop can be navigated using the mouse button).
You can also use a command like this one to show the processes memory in megabytes and the process path, but generally htop and top are my favorites.
Let me know how it goes.
Thanks! I have now tried atop, top and htop. I didn’t know these existed. Fascinating to watch the server operation in real time, not that it means too much to me at the moment. It turns out the the ‘mercure’ module was the culprit. Installing an upgrade sorted that out.
I am alway impressed by smart guys like you who can rattle off lines of code like “ps auk …”
I’m now reading through tutorials and making a list of useful commands and code snippets.
Many thanks for your help.