These things can slow down FogBugz performance:

  1. Email Server Issues? Determine if this only happens when automatic email notifications get sent. Is it the case that assigning a bug to a person with email notification turned on causes a delay, but assigning a bug to a person with email notification turned off happens instantly?If this is the case, the problem is related to your SMTP mail server. It’s possible that the mail server is remarkably slow. More commonly, it’s caused by a firewall between the mail server and the FogBugz server. See Troubleshooting Email Notification Problems for more details, especially the section titled “Check that you are not blocking ident traffic” and the notes on nslookup right above that.
  2. Database Authentication? If it happens for all page loads, it may be an authentication issue. In Windows: If your connection string has this in it:Integrated Security=SSPI;…then switch to name and password in the connection string, using a SQL Server login that has db_owner rights and access to the FogBugz database. Example:

    Server=myServer;Initial Catalog=myDatabase;User Id=myUserID;Password=myPassword;MultipleActiveResultSets=true;

  3. DNS Issues? If you are not using Windows Integrated Security, and are passing a username and password for a database login, and page loads are still slow, one thing to try is the following. In the connection string, shown above, note the server name part:Data Source=SERVER-NAME-HERE;Instead of using the server name, use the IP address. Or, if the database is on the same machine as the web server, use:

    Data Source=[localhost];

    This has been known to work in some cases.

    MySQL: if you’re using FogBugz 7.0 or later, your connection string should start with DRIVER={mysql}; If it starts with Driver={MySQL ODBC 3.51 Driver}; change it.

  4. Slow SQL Server? If you use SQL Server with FogBugz, try restarting SQL Server. If after restarting SQL Server, an event in Event Viewer comes up as:supersocket info: connectionlisten(shared-memory LPC)) error 5Go to http://support.microsoft.com/kb/815249 and execute the workaround listed there…
  5. DB time-outs with MySQL? If you use MySQL with FogBugz and you see errors about database time-outs, see this post on debugging MySQL
  6. Virus Scanner?   McAfee Virus Scan may be monitoring all files. Other users found that this killed their performance (presumably because every time SQL Server hit the disk, McAfee was checking the DB files for viruses. Updating McAfee to the latest version and having it ignore the DB files completely solved the problem).