MySql overload using all memory on the droplet

Posted July 2, 2013 12.6k views
Hi, Im migrated a buddypress site to a droplet with 512mb . and im having some issues. The first instalation was fine but when i did the dump / export tables from wordpress, the mysql started to crash. Then i created the swap and it stopped to crash BUT still couldnt use the server. Then i did the changes on my.cnf and apache.conf ( and i can use it for 1 minute than it overload again but didnt crash This is my free -m total used free shared buffers cached Mem: 491 482 8 0 1 17 -/+ buffers/cache: 464 26 Swap: 511 506 5 The database only have 8mb... its not possible to be eating all the free memory...

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.

Submit an Answer
11 answers
The best solution would be upgrading your droplet as it seems like 512MB is not enough for your application stack.

You can try to disable mysql's InnoDB engine as it takes up a lot of RAM:
You sir is a life saver..

I tried the skip-innodb but with no use.. the service wasnt working.. didnt knew that innodb was such a memory hungry
MySQL is probably crashing due to running out of memory. Is everything working fine now?
It was but wp_users and some aspect of my buddypress use innodb.. so i turned it on again but with a few changes.. (>..

I did some test.. always checking free -m to see the memory use... on the first 10minutes.. all fine.. only using 128mb and no swap (i enter the site.. did some stuff there.. the memory usage got a little bit high but released after) but ... pass the 10 minutes up.. it consume everthing again... what could be happening?
total used free shared buffers cached
Mem: 491 485 6 0 0 10
-/+ buffers/cache: 474 16
Swap: 511 509 2

Does my site have all that traffic and i dont know..? pass another 5 minutes and everthing get back to normal...

total used free shared buffers cached
Mem: 491 308 183 0 4 42
-/+ buffers/cache: 261 230
Swap: 511 92 419
Seems its not configuration... seems like bad programing.. im checking it...
I don't recommend running a whole LAMP stack with InnoDB enabled on a 512MB droplet as it won't have enough resources and will run out of memory and cause processes to crash.

You should upgrade to at least a 1GB droplet.
I upgrade..
total used free shared buffers cached
Mem: 995 871 123 0 0 14
-/+ buffers/cache: 856 138
Swap: 1023 584 439

Im afraid it will consume all again..

... can i have more than 1 swap file?
There's actually 856MB used, the rest are cached. The memory usage looks fine - you shouldn't experience any more crashes.
installed memcache and xcache.. oh boy.. huge difference !
Previous 1 2 Next