I had been trying to puzzle out just how much RAM / CPU I desired in a minimum to host a wordpress blog, and that i happened on something rather annoying.

I'm using wordpress_super_cache to produce static pages from the wordpress posts and lighttpd + an LUA script to redirect a person towards the wordpress_super_cache-produced page immediatly. This protects alot of server assets. Despite a 500 Mhz CPU and 128 RAM I possibly could serve ~120 pages per second.

Really the only load comes when wordpress_super_cache needs to produce a html file because none has been manufactured yet, or perhaps a publish continues to be up-to-date / a comment added. Which means this mostly occurs when a brand new publish is added, as this means all the index pages have to be up-to-date, because all posts are moved 1 place lower. Now take a look only at that.

enter image description here

I do not realise why worpdress is moving a lot in to the cache. Sure, pages following the initial one take 3 instead of 13 seconds to create since the cache is just filled around the initial load, however it required 3 seconds to begin with, so why do loading stuff in to the cache whatsoever?

The main reason I wish to eliminate this behavior happens because I wish to host in a minimum and also, since I'm using wordpress_super_cahce + an LUA script to redirct there imemdiatly, this caching stuff is making the server (when its at 128 RAM) very slow, nearly unresponsive even, for not good reason. Which does not make sense at all whatsoever because I'm essentially asking for the identical page to become produced. I would like wordpress to totally disregard the fact you will find 1000's of publish, and merely concentrate on the 10 which are being asked for.

tldr version:

How do you affect the wordpress code to ensure that it entirely ignores all posts, aside from those being asked for around the index page(s), to avoid a lot of unecessary stuff being written towards the memory cache.

PS: I published this here and this is not on server fault because I'm fairly sure it's wordpress' coding leading to this, and never server software.

You will find various ways to create Wordpress site scalable and actually Wordpress can be displayed quite kick ass.

As you've 55000 posts within the blog, it is best to implement load-balancer and cache content to become offered with a different server. It's difficult to go over the entire factor here since it is huge. Browse the video from Ryan Allen from Envato (The organization behind Themforest, and all sorts of the tuts++ sites) where he describes the way they scale Wordpress site. http://blainsmith.com/post/3619881611/scaling-wordpress

If you have that much of posts and that i assume they are important. So, you may wanna provide a consideration on a bit more costly hardware and also the cache server, load-balancer solution.