No Worries. Your LAMP / WordPress RAM use is primarily based on a chunk for the database and a chunk per Apache process. The Apache processes hang around after use to handle http timeouts and to then remain available for another http request. The size of the RAM chunk is related to the size and number of plugins you add to WordPress.
On a system restart your system will stabailise to its true RAM requirements until http activity starts to trigger the persistent Apache processes.
If you are stable now and your site is low use you won't have trouble for a while. Once the robots find you though this will change especially the Baidu robot. They can hammer your site and cause your apache to chew up all the RAM and start using your swap space.
Stable non-swapping RAM use is related to # & size of plugins
No Worries. Your LAMP / WordPress RAM use is primarily based on a chunk for the database and a chunk per Apache process. The Apache processes hang around after use to handle http timeouts and to then remain available for another http request. The size of the RAM chunk is related to the size and number of plugins you add to WordPress.
On a system restart your system will stabailise to its true RAM requirements until http activity starts to trigger the persistent Apache processes.
If you are stable now and your site is low use you won't have trouble for a while. Once the robots find you though this will change especially the Baidu robot. They can hammer your site and cause your apache to chew up all the RAM and start using your swap space.
Cheers,
Tim (Managing Director - OnePressTech)