All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

So, the last time someone complained about rt.cpan.org's performance, I dropped in some new logging. And actually caught a bogus query that had some Serious performance implications. A quick index fixed it right up. And we've been watching the logs since then. Of the last 25,000 page loads, 95+% have rendered fully to the browser in under two seconds.
What I need to know (and a journal post isn't the right place for this. mail to jesse@bestpractical.com would be much better) is
1) What was slow. What page

The cpan-questions address on the front page of the site will log it in the right place.

I have a minion with a whole slew of tasks related to fixing up the source for publication and fixing a couple of the worst _known_ performance issues over the next couple weeks. When we do that, we'll be able to cpan rt.cpan and move bug tracking to rt.cpan.;)

I've been sending stuff to that address, and apart from a short period after the most recent upgrade, they fall into the bit bucket and I never know what state they are in after an initial "thanks for the message" response.

FYI, I'm following along and if it turns out that hardware is part of the problem, TPF will do what we can to fix things. As it is, it appears Jesse is on the case and has a few things to try before we buy new hardware.