Optimización de recursos en sitio web basado en WooCommerce (Ref.: VDM)

Tenemos que sitio alojado en nuestro cloud (160GB SSD, 5 cores, 15 GB RAM) que está consumiendo demasiados recursos. Cada cierto tiempo ejecuta tareas que exceden los límites de nuestros recursos (CPU y RAM) y genera que todo el cloud se caiga afectando a los demás sitios que tenemos alojados. No sabemos exactamente cuál es el proceso que genera estas caídas, pero suponemos que uno de ellos puede ser cuando nuestro cliente actualiza el listado de productos desde un CSV. Al hacerlo, da un error 500 (Internal Server Error/Connection Timeout). Estos microcortes por lo general duran 5 minutos y luego vuelve todo a la normalidad, pero se repiten con frecuencia. En el soporte técnico de Siteground nos recomendaron estas tareas de mejora y necesitamos un web developer que nos ayude a realizar estas correcciones para evitar que continúen estas caídas: It looks like the server has reached high load recently: High load (23.16) reached! Critical load (23.16) reached! Killing all php,ftp,smtp,mailnull,archivers procs! I recommend that you optimize the database of the website as it is as close to 3 GB large and as a result it generates slow queries: [login to view URL] [login to view URL] It appears that the [login to view URL] script of the website was heavily active. The majority of the time when we see the problems in an [login to view URL] file is due to the requests made by installed plugins. These plugins make the WordPress backend slow by sending requests to attain a certain functionality such as firing up a pop-up or updating a social sharing counter. These plugins make tons of these requests to stay functional. The [login to view URL] file itself is not a bad thing when used correctly. It is part of the core and was added by the WordPress development team in version 3.6. The purpose of [login to view URL] is to create a connection between the browser and the server using AJAX. This allows for extended functionality such as improving auto-saving, revision tracking, login timeouts, session management, and notifications about a post being locked when there are multiple editors. The issue can be resolved by following an article from our knowledge base: [login to view URL] Also, the [login to view URL] script was excessively active. Cron is a UNIX command for scheduling jobs to be executed sometime in the future. It's normally used to schedule a job that is executed periodically. 
 WordPress uses a file called [login to view URL] as a virtual cron job, or scheduled task in order to automate things like * publishing scheduled posts * checking for plugin or theme updates * sending email notifications * backing up * WordPress automatic updates * ... and so on. You can replace the WordPress cron with a real one in order to have the issue resolved, this way: [login to view URL]