Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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 were you on. What did you do. 2) How slow was it? 3) When did this slowness happen. The machine isn't really breaking a sweat at this point, which suggests it might be something else. We've been working with ask to move the application to a server run by perl.org in their colo facility. If it _is_ hardware and having the app run on perl.org's hardware, I'm certainly not adverse to buying another box to fix a performance issue, but I need to _see_ the problem. The scale rt.cpan.org is operating at just isn't a volume that should be giving RT pause. (Ok. The pun was horrible. I'm sorry.) Are any of you folks who are interested in a faster rt.cpan willing to spend a bit of time showing me what you're seeing ?
    • Here's what I am seeing right now. Loading page http://rt.cpan.org/Public/ [cpan.org] took 3.584 seconds according to FasterFox, but the in page time reads 'Time to display: 0.181015'. My ping time to rt.cpan.org is about 90 ms.

      My search for bugs on Apache::Dispatch http://rt.cpan.org/Public/Dist/Display.html?Name=Apache%3A%3ADispatch [cpan.org] took 7.67 seconds according to fasterfox, and page time reads 'Time to display: 5.985952'. My search for bugs on mechanize http://rt.cpan.org/Public/Dist/Display.html?Name=WWW%3A%3AMe [cpan.org]

    • One example for me...

      Resolving a bug, with comment.

      Time to load, around 20+ seconds.

      Time page says it took, 3.5 seconds.
      • Adam,

        You're a developer. You _know_ how to report bugs. (You also have tools like YSlow and Firebug which can give you real numbers)

        But

        1) what IP are you coming from
        2) What URL were you starting from.
        3) What URL did you end up at?
        4) how long did one of the aforementioned tools tell you it took?
        5) What _exact_ time did it happen at?

        What you gave me is basically no better than "it's slow. and lied to me." - Which isn't much to work with.
        • I was in a hurry :)

          Point me at the RT queue for rt.cpan.org and I'll file it properly.
          • 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.

              Is the queue actually visible somewhere?

              • 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.