Trac

[Charles]

Does anyone here have experience administrating Trac?

[Charles]

Trac is still slow. I haven't had time to diagnose the problems. Basically the MySQL process is getting pumped up to 99% CPU consumption. Note that the discussion forums (phpBB) use MySQL and are responsive. Also, Apache is responsive with static files. So this leaves Trac as the culprit.

[Charles]

Also, restarting mysqld doesn't resolve the problem. I even have a cron job to restart nightly, but that does not improve the situation at all.

[agustech]

I am having problems loading forum sometimes, maybe because Trac puts CPU at 100%.

[Charles]

The entire server was unresponsive for several hours overnight and I had to reboot it. Other than that, I have found the forums to be responsive even when mysqld was cranking 100% of CPU.

I had to do a reload on a few pages then due to caching issues; my browser thought the stylesheets were still missing.

Currently, I have disabled Trac and mod_python to see if mysqld cranks up again.

[Charles]

mysqld does not crank up again if Trac is off.

For now I've applied the following band aids:

* Turn Trac off at 6:00AM ET every day and restart mysqld. Turn Trac back on 20 minutes later.

* Restart mysqld at 40 minutes past the hour, every hour.

A lame approach, but all I have time for right now.

[hopscc]

Is there any progress on this ?

For me Forums are now generally OK. ( slowish but bearable)
trac access is usable for an hour or two after (L.A )6.30 pm ( sub 5 sec) but turns to custard ( > 2 minutes) after that
currently (~ 11.00 pm L.A. time) theres no response in waiting for load to complete for more than 5 minutes...

If theres no success with the trac forums/bug reports /fixes ( whatever the trac problem is) - whats the fallback option as ( for me at least)
this is making the ticket/change tracking pretty much useless (mostly inaccessible) and will probably make pushing changes against tickets impossible.

[Charles]

To make Trac occasionally useful, it is shut down on the hour for 10 minutes by cron. So it's completely out for 1/6th of the hour, always at the same time. After it comes back up, it's generally usable and can even be fast, but will be still be slow for some operations like updating a ticket.

It gets slower the longer it is up. Sometimes I cannot use it around the :50 minute mark.

Overall, I am able to use it, but it's not pretty.

I've had zero performance problems with the forums. In fact, they respond well even when Trac is making mysqld consume the CPU.

There is no fallback option at this point. I was hoping someone in the community would have the time and/or experience to take a look at this, but that hasn't been the case.

Of course, it would be nice to have a Trac/Cobra, but such a project hasn't even been started.

[hopscc]

Is there nothing in the trac site (or anywhere else) about this as an issue for any other project using it?
I did a quick skim a couple of weeks ago (trac site) and didnt see anything but didnt get back to looking????

[hopscc]

Hmm. Tested accessing items off timeline on trac 10 mins past hour just after trac comes back up again

Timings are all over the place 3 secs min to 2.5 mins max - theres a rough correlation on first access to
the size of the changeset but thats about it
second or later accesses to same changeset are sometimes shorter (3 secs) and sometimes longer ( 1-2 mins) .....