Shared Hosting
Shared HostingKnowledgebase
Portal Home > Knowledgebase > Articles Database > Working out what eat all the memory
Working out what eat all the memory
 |
 |
 |
Posted by llocalmark, 10-25-2013, 11:18 AM Hi, I have a VPS with 4 gb memory, and most the time it runs happily at 1.3 gb memory. It has a handful of low usage websites on it, but every now and then, rarely, it runs out of memory and starts killing off processes. When I look at the logs, there isn't anything that sticks out like a sore thumb, perhaps just the number of php-gci's (the sites are set up as fcgid ), but the number of httpd is around a dozen at the time of the crash. Doesn't sound like a lot to me. Is there something I should be looking for specifically? Should I be tweaking some settings, or just buy more memory. Are these just unlucky spikes, they are rare? (I have been testing Varnish on another server, but there are lots of config issues to deal with before I could consider it on my live server, and one I can't even find a solution for) Your expertise is welcome, I'm sure you will need more technical details, so please ask.
Posted by kevincheri, 10-25-2013, 08:21 PM Did you notice any specific times this causes?. You may need live monitoring of the server through top command to see what eating them up.
Add to Favourites 
Print this Article
Also Read
