|RT is so slow
||[Sep. 29th, 2007|12:16 pm]
Dear Jesse Vincent,
rt.cpan.org is still unusably slow. I don't care the specs of the box, how it's configured, or who runs it. It reflects poorly on your company and your software and I'd be embarrassed if I were you to have rt.cpan.org still running.
Please host this yourself, or buy perl.org a new box for this, and maintain it for them. Or take your name off the front page of rt.cpan.org to distance yourself from it. Either way.
(just grumpy because people are still filing tickets in it, most of which I want to close with WONTFIX or REJECTED, but the system's too slow to even let me do that....)
So note to everybody else: I will ignore your rt.cpan.org tickets and patches. Use the mailing lists. My inbox is my ticketing system.
2007-09-29 08:27 pm (UTC)
It has an email interface.
2007-09-29 09:43 pm (UTC)
So let's shut down the web interface and only advertise the email interface. Previous arguments still hold.
2007-09-29 09:49 pm (UTC)
Oh, I wasn't arguing for or against anything. You mentioned a specific task that was taking you long, I was just pointing out something that could help. (I don't actually know how to WONTFIX from email, so you'll have to spend time figuring that out too, but it may be more pleasant than waiting on web forms).
I could probably set up a Bugzilla instance that performed better than RT, but it's hard to say, really. The CPAN RT has a *lot* of queues. And Bugzilla's email interface is just slightly below RT's email interface.
2007-09-29 11:17 pm (UTC)
So, about a month ago we went through a maintenance cycle with it and since then I've been seeing ~1s page load times.
What's hurting you right now?
(Also, perhaps the CLI would make you happier?)
2007-09-29 11:28 pm (UTC)
The numbers that RT shows at the bottom left corner were saying 5-10 seconds. Nothing fancy... just clicking around, looking at bugs, occasionally trying to close one.
2007-09-29 11:30 pm (UTC)
Shoot me a couple URLs?
I totally believe you but can't replicate it. Being able to replicate it would really help me fix it. Can you shoot me mail with a couple of things that hurt?
First page after logging in ( index.html): Time to display: 25.971506
Opening the catalyst queue: Time to display: 20.512825
Opening first available bug: Time to display: 90.957272
Those are server-side timing (your neat thing in the footer), it felt a bit slower, but I guess the signals takes some time to cross over to europe.
2007-10-24 04:34 am (UTC)
Re: Shoot me a couple URLs?
We're happy to cover the cost of a new box, we even havea bunch lying around now that we can donate. Just sayin...
2007-09-29 11:17 pm (UTC)
Certificate error too.
I didn't know what the site is used for, so I typed in http://rt.cpan.org and was greeted by a certificate error. So, it's not only slow but tagged as suspicious by many spyware systems and possibly inaccessible to many corporate users.
Hi, Brad! :)
Thank you for Live Journal!
From Russia with love! :))
too bad you can't close those tickets with an email.
as easy as people submit them, at least.
2007-10-02 09:13 am (UTC)
The kicker is..... it is hosted by best practical
The kicker in this is that best practical is hosting the rt.cpan.org:
; <<>> DiG 9.3.4 <<>> rt.cpan.org
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34676
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;rt.cpan.org. IN A
;; ANSWER SECTION:
rt.cpan.org. 86390 IN A 184.108.40.206
;; Query time: 1212 msec
;; SERVER: 220.127.116.11#53(18.104.22.168)
;; WHEN: Tue Oct 2 10:46:01 2007
;; MSG SIZE rcvd: 45
From the traceroute:
8 ge-6-2-903.car5.london1.level3.net (22.214.171.124) 417.911 ms 413.228 ms 424.360 ms
9 ae-31-55.ebr1.london1.level3.net (126.96.36.199) 514.603 ms * ae-32-56.ebr2.london1.level3.net (188.8.131.52) 371.385 ms
10 ae-1-100.ebr2.london1.level3.net (184.108.40.206) 380.154 ms ae-4.ebr1.newyork1.level3.net (220.127.116.11) 648.234 ms ae-1-100.ebr2.london1.level3.net (18.104.22.168) 447.611 ms
11 * ae-4.ebr1.newyork1.level3.net (22.214.171.124) 411.519 ms ae-5-5.car2.boston1.level3.net (126.96.36.199) 417.656 ms
12 co-location.car2.level3.net (188.8.131.52) 414.588 ms ae-5-5.car2.boston1.level3.net (184.108.40.206) 635.772 ms co-location.car2.level3.net (220.127.116.11) 415.281 ms
13 co-location.car2.level3.net (18.104.22.168) 416.055 ms diesel.bestpractical.com (22.214.171.124) 373.968 ms co-location.car2.level3.net (126.96.36.199) 414.445 ms
Maybe best practical need to throw more hardware at the situation?
Time to display: 11.409288
Taking 11.4 seconds to render the frontpage is insane.
2007-10-02 04:44 pm (UTC)
Re: The kicker is..... it is hosted by best practical
I was hosting at a provider that routed most of their traffic through Level 3. The routing was horrible over long distances, many of my customers that were over a few hundred miles from the data center complained about the speed. I changed providers and one response from my customer was 'holy shit thats a lot faster'. So maybe it's not RT but the network that's causing the slowness.
I setup a Xen box on a much faster box with a faster database (than the one BP is using for it anyway).
We took a while to get the basics going though and I think it stalled on the BP guy who was working on it went back to school or some such. :-/