josedieguez
No, that’s a very common mistake. When you run top and don’t see anything suspicious other than a bunch of stuck lsphp or phpfpm processes, each with little CPU and RAM usage, the next step should always be:
mysql -t -e "SHOW FULL PROCESSLIST"
Most of the time, slow queries are the culprit. The WordPress ecosystem is full of themes and plugins that generate inefficient queries, and this happens a lot.
If you stick to well-known, widely tested plugins, you can avoid most of these issues. But in shared hosting, you don’t control what clients install on their sites. A single bloated plugin or script can bring even a powerful server to its knees in minutes.
To tackle this, many hosting companies use CloudLinux, while others, such as HostGator and companies that haven't adopted CloudLinux, develop their own in-house solutions to enforce strict boundaries and prevent resource abuse.
