Recently, I have been talking to more and more people who are complaining about the server usage that WordPress is putting on their hosting. Some are buying inexpensive shared hosting accounts, some, like me, are on a managed VPS, while others have their own dedicated server.
The amount of server resources used by WordPress varies wildly for these people, with some coming across horrible performance walls with less traffic than myself, and others having much lower usage levels on their servers than I do. The part that bothers me so much is that there isn’t a nicely compiled guide out there to performance tune WordPress hosted blogs.
Sure, there are caching plugins, but going beyond that Matt Mullenweg has said that Automattic has helped hosting environments with their situations so that they can better support more traffic with the resources they have available, and so why isn’t there a basic server performance guide for WordPress? A best practices guide when setting up a server for displaying the PHP pages that WordPress needs to generate, or dealing with MySQL calls, or best practices for caching. Which applications should we be using to get the most performance from our WordPress blogs?
If there are so many great tips out there for making WordPress run effectively in high traffic situations, where is the organized guide for web hosts, or server owners? This could resolve so many issues that my friends are having, and help me reduce the load on my own VPS. Sure, it would take some time to compile, but the guides out there for serving up PHP pages and optimizing MySQL are currently difficult to understand, with little information on the overall benefits with relation to WordPress itself.
Come on WordPress ninjas, it is time to write a best practices guide for server administrators.
Related Blogs
- Related Blogs on WordPress
- Top WordPress Plugins For Every Type of Blog – The Best of the Best!
- Thesis – a WordPress Theme Design Worth Considering
- WordPress 2.6 Goes Live
Originally posted on September 13, 2008 @ 6:53 pm