I just went through a week of hell trying to save a VPS server with 1.3GB of RAM from crashing in part because of YARPP. I have a site that serves 600,000 pages a month, across 9000+ posts. I love the fact YARPP generates related posts on the fly (in particular because what is deemed to be related is always drawn from the newest content on your site), but it appears that YARPP trawling through my database of 9000+ posts 20,000 times a day is too much for the CPU and server.

Does anyone have any advice on this, or fixes / tweaks for heavy resource use when using YARPP?

The other plugins I've seen, including the follow, generate related posts when you create the post. That's okay if you install the plugin from day one. But 9000+ posts down the line, it means that only your newest posts (after installing the alternative plugins) would have related posts.

I need to find a way through this conundrum, because related posts is one of the most important ways to keep visitors onsite.

link|improve this question
just cache the rp query until a post is created / deleted – One Trick Pony Sep 1 '11 at 8:33
@jb510 not being able to leave comments is not a valid excuse to misuse answers. It doesn't take a lot to be able to leave comments, please focus on proper answers before then. – Rarst Sep 1 '11 at 10:24
Rarst - understood, still learning some etiquette. I deleted commentary portion and left answers portion, please consider undeleteing. – jb510 Sep 1 '11 at 21:23
You really need to include more info. What version of YARPP are you running? what caching are you doing and with what? W3TC? SuperCache? BatCache? Memcached? APC? etc... – jb510 Sep 1 '11 at 21:24
@jb510 I tried everything. My setup was: Nginx(reverse proxy)-APC-Apache-CloudFlare. Latest WP, latest YARPP – Ian Douglas Sep 2 '11 at 20:27
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown

Browse other questions tagged or ask your own question.