lammert - 1:46 pm on Mar 14, 2010 (gmt 0)

It is difficult to say from this logfile if it causes a heavy load on the server. But the message "your wordpress usage has outgrown and is the prime cause of crashing mysql server every single day" is a red alert to me. No site on a shared hosting configuration with 2000 visitors each day should be able to bring a MySQL server on its knees. That is either a signal of bad configuration of the server, overselling, or the statement is only there to threaten you in a higher paying hosting plan.

Running a WordPress blog myself, I can hardly believe that with this amount of users they can claim that you are reaching the 20% CPU resource limit. 2000 visitors with each 4 pages gives one pageview every 10 seconds. 20% CPU resources would indicate at least 2 seconds CPU processing per generated page. Unless your blog is full of resource intensive third party plugins, that is hard to believe.

The only exception to this rule is when you use WordPress with static pages, not in blog mode. WordPress was originally a piece of blog software where posts are ordered on date and time. That part of the software is extremely efficient. Somewhere around version 2.0 the possibility of static pages was added to accommodate for about pages, privacy policy pages etc. Static pages are not stored in the regular posts structure, but in another way which happens to be extremely inefficient as soon as the number of static pages increases to about 100 and permalinks are used to reference to them.

There has been a thread about this recently in the supporters side of this board at [webmasterworld.com...]

If you don't want to move your site to another hosting situation, you can try to improve the current situation by switching on caching. With caching WordPress tries to store frequently used parts of pages in static files. Whenever these parts are needed, they are just read from disk instead of queried from the database which reduces CPU usage and increases page load speed.