Hi. I will soon (today or early tomorrow) get back to Herbert with two things: - profiling instructions - possible solution Also, he mentioned today in irc that he's going to add a tmp fix by restarting apache periodically, since problem starts after an hour of its work (not sure if I was supposed to talk about this :)). 16 квіт. 2015 17:42 "Richard Eisenberg" пише:

Trac is bac.

But is there anything we can do to improve reliability?

Thanks! Richard

On Apr 16, 2015, at 10:19 AM, Richard Eisenberg wrote:

...

Hi devs,

Trac isn't working again. In an entirely unscientific study, 4 out of the last 5 sessions where I tried to access Trac, I was unable to.

If ghc.haskell.org is getting slammed, is it possible to disconnect Trac from that name and instead just publish some IP address until we have things working better? (Apologies if that sentence doesn't make any sense at all. I've dealt very little with these sorts of issues.)

Thanks, Richard _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

How would non-developers file or comment on bugs in that scenario? BR, Niklas ----- Ursprungligt meddelande ----- Från: "John Wiegley" Skickat: ‎2015-‎04-‎17 19:52 Till: "Richard Eisenberg" Kopia: "ghc-devs@haskell.org Devs" Ämne: Re: Trac is soul-extinguishingly slow

...

...

...

...

Richard Eisenberg writes:

If ghc.haskell.org is getting slammed, is it possible to disconnect Trac from that name and instead just publish some IP address until we have things working better? (Apologies if that sentence doesn't make any sense at all. I've dealt very little with these sorts of issues.)

I'm wondering if, in the interim, we couldn't do two things: 1. Make the public facing side of Trac read-only, by generating a static copy of the site nightly and exposing that via nginx. Bug data would be one day old at most, but it could still be searched, browsed, etc. Just not interacted with by non-GHC developers. 2. Give the GHC developers an SSH login to the machine running Trac, so that, by way of a port forward and an edit to /etc/hosts, they could have secure, direct access to the bug tracker. I realize this is sub-optimal in many ways, but it's relatively easy to setup and would cure all current problems until a better solution is found. John _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs