Hmmm, Trac is running a high CPU now. I'm looking at it.
We had a problem a few weeks ago with aggressive webspiders
crawling/indexing the changesets for GHC, which put Trac at a
relatively high load as it computed lots of diffs. We redirected the
changeset view temporarily - I'm looking at why it's all cranky now.
FWIW, Phabricator is located in an entirely separate part of the world
with its own dedicated resources (including buildbot for patches), and
should be unaffected. In fact, I think I know how to speed up the page
load times even further for Phab...
On Fri, Sep 5, 2014 at 4:34 PM, Joachim Breitner
Hi,
Am Freitag, den 05.09.2014, 03:21 -0500 schrieb Austin Seipp:
Update: Trac should be much more responsive now (and Hackage too), but Hackage still needs more investigation. Still ongoing for the moment...
I’m still observing bad response times, and errors like "database locked".
If they are gone when I do the HIW Trac+Phab demo, that’d be great.
Greetings, Joachim
-- Joachim “nomeata” Breitner mail@joachim-breitner.de • http://www.joachim-breitner.de/ Jabber: nomeata@joachim-breitner.de • GPG-Key: 0xF0FBF51F Debian Developer: nomeata@debian.org
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
-- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/