0

2

Fogbugz has been very slow since we upgraded to 8.0.26 (Unix install).

When I run 'top' on the Fogbugz server, MySQL and Mono regularly take up a large chunk of the available CPU and Memory: Mono is currently using 184%CPU and 14%Memory at the moment. The server has 4 CPU cores and 3GB of RAM.

I've noticed the resource hogging behavior for the last few days. At times the site actually becomes unavailable. When this happens the only solution I have found is to stop the fogbugzctl daemon and wait for Mono and MySQL to calm down. Typically the Mono process never comes down and continues reporting 400% to 9999% CPU usage in these extreme cases. I am eventually forced to kill the rogue Mono process and restart fogbugzctl.

We've seen some of this type of behavior in past releases, but never to this degree. Do you have any suggestions on debugging this problem? or any ideas on potential culprits to investigate?

flag

2 Answers

1

This is an ongoing headache for pretty much everyone. There doesn't appear to be any specific trigger, other than that after some amount of time, the mono worker process starts behaving poorly. The only remedy is to restart it, possibly using kill -9 if the process is unresponsive to normal shutdown procedures. Preemptively restarting things appears to prevent recurrences, and is something we're looking into doing more automatically.

link|flag
Is this a symptom in Windows installations as well? We're looking to purchase Kiln and that would require a Windows installation at this point. We are trying to convince a large number of users to adopt and use Fogbugz, but they are seeing this slowness and are reluctant to buy in. For our team, I think this is the highest priority item we would like to see fixed. Restarting Fogbugz every day isn't really the solution I hoped for. – Mike Caron Nov 19 2010 at 15:11
No, it only affects linux and mac installations. – Ted Nov 19 2010 at 20:18
0

Please upgrade to 8.1.4. The Case History plug-in goes and rebuilts the history of the entire install to give you sexy reports.

Since 8.0.26, we have improved how it goes about this backfill, so it should be a bit less onerous for your machine. In any case, though, this should improve over time. (Or actually just stop happening at some point, with the exception of the ongoing issue Ted pointed out.)

link|flag
Rich - I'm still observing similar issues in 8.3.42 on RHEL5. Mono just keeps sucking up RAM and fogbugz stacks up sleeping MySQL processes, and FB eventually grinds to a halt. Killing the mono process clears the MySQL processes and gets everything going again, for a while. Any more troubleshooting ideas? – Brian Campbell Mar 8 2011 at 19:06

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.