Changes between Version 2 and Version 3 of TracPerformance

Timestamp:

Aug 7, 2009, 11:44:26 AM (15 years ago)

Author:

Christian Boos

Comment:

started an unsorted list of possible performance hits

TracPerformance

@@ -14 +14 @@
 In this page we'll try to collect all the various pieces of information related to performance, in order to compile a "checklist" that can be followed when trying to troubleshoot a performance problem, or simply when one wants to get a better performance out of his Trac installation.
 
+== Unsorted ==
+ 
+For getting this started, here's a list of some of the common problems:
+ - serving static resources through Trac: for best performance, they're better served by the web server, see TracCgi#MappingStaticResources (well, and of course, if you're using Trac deployed as a cgi, don't come complain about performance!) [[br]] ''(Note: we should probably move the ''mapping static resources'' section to another page, e.g. [wiki:TracModWSGI])''
+ - if using mod_python, only use latest version (3.3.1); prefer mod_wsgi (>= 2.4) (daemon mode)
+ - repository resync failure which results in a resync attempt for every request - easy to spot in the Trac log (see ticket:7940#comment:36); often due to the "prohibited" MySQL/MyISAM combination (#8067)
+ - running Trac under QEMU is slow (7940#comment:42)
+ - possible issues when using mod_deflate (#8534,  googlegroups:trac-users:ab070d251f5a0d11); on the other hand, some people have good results with mod_deflate and advise using it (["TracDev/Performance/0.11.5#HowItimed"])
+ - use of `restrict_owner = true` can be (very) slow on some installations, see  restrict_owner setting? Is it enabled in those problematic installations? (see #4245, #8034, #8212 ...)
+ - there was a bug up to 0.11.4 which could cause 100% cpu usage on some platforms (#7785, fixed in 0.11.5)
+ - some plugins seem to have a high impact on the performance (["TracDev/Performance/0.11.5#customizationsandplugins"])
 
 ----