Basic explanation of resource consumption when using WordPress PHP interpreter and query the MySQL database.
One thing I have noticed in all my time in the world of hosting and web hosting is that very few webmasters have expertise on how the CMS they are using or how to run the PHP interpreter.
Most providers when exposed public characteristics of a shared hosting plan discussed the monthly transfer the maximum usable or usable disk space, but rarely bean consumption is causing a CMS in terms of resources and CPU resources RAM.
Although not directly visible anywhere, every time a visitor comes to a website created with a CMS written in PHP, consumption of important resources occurs that talking about very large volumes of traffic can be seen as a major problem .
We should note that all the plugins we install in our WordPress will more or less on website performance impact if the hosting account has not allocated sufficient CPU and RAM resources of a poor choice of plugins could reach significantly saturate resources and leave the site offline.
Besides making use of PHP interpreter must also take into account the use of RAM and CPU that performs the MySQL server where data are stored WordPress installation, so that the more queries to the database made the plugins and theme, the greater the consumption of resources WordPress and increase the response time of the web site.
This is an example of consumption of some of the most used for WordPress plugins:
- BuddyPress with all active modules: 11,64MB and 8 queries.
- bbPress with default settings: 4,82MB and 26 consultations.
- Jetpack (base) and WordPress.com logged in default: 9,10MB and 27 consultations.
- Wordfence with the default settings: 2,72MB and 28 consultations.
- iThemes Security with the default settings: 1,20MB and 12 consultations.
- WooCommerce with default settings: 5,51MB and 18 consultations.
- WordPress SEO by Yoas t (data falsified by the plugin): 3,02MB to 1 consultation.