Changes between Version 14 and Version 15 of TracPerformance
- Timestamp:
- Jan 4, 2015, 8:46:43 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracPerformance
v14 v15 1 = Trac and Performance =1 = Trac and Performance 2 2 3 3 With Trac 0.11, the ClearSilver template engine was replaced with the Genshi template engine, but with its increased flexibility, Trac also became slower and memory hungry. As memory usage seems now mostly OK (#6614), there are still many concerns over Trac's performance. … … 12 12 This page collects Trac performance issues, solutions and troubleshooting. 13 13 14 == Check your installation ==#Installation14 == Check your installation #Installation 15 15 16 16 If Trac is not installed correctly, performance will suffer. The most obvious mistake is installing Trac as a CGI script. Even for testing, there are better alternatives, see [TracStandalone tracd]. … … 27 27 - ensure an image has been configured as the trac logo in the top left. The default install from Ubuntu 10.04 for example does not include a default logo and this makes pages slow to load. 28 28 29 == Check your configuration ==#Configuration29 == Check your configuration #Configuration 30 30 31 31 Several settings enhance Trac in one way or the other, but have a performance cost, which in some cases can be large. 32 32 33 === `[timeline]` ===#timeline-section33 === `[timeline]` #timeline-section 34 34 - `default_daysback` set to a high value might introduce quite some load, depending on the activity. 35 35 Pick an appropriate value for your site. … … 39 39 depending on the quantity of changesets to process 40 40 41 === `[ticket]` ===#ticket-section41 === `[ticket]` #ticket-section 42 42 - use of `restrict_owner = true` can be slow on some installations (see #4245, #8034, #8212 ...) 43 43 44 == Check your [TracLogging trac.log] ==#Log44 == Check your [TracLogging trac.log] #Log 45 45 46 46 Search for the following: … … 52 52 A mis-configured or simply slow mail server make Trac appear very slow (#3220 and numerous others). 53 53 54 == Unsorted ==54 == Unsorted 55 55 56 56 - There was a bug up to 0.11.4 which could cause 100% CPU usage once in a while on some platforms (#7785, thought to be fixed in 0.11.5, but re-opened since). 57 57 - Some plugins seem to have a high impact on the performance, see ["TracDev/Performance/0.11.5#customizationsandplugins"]. 58 58 59 == Profiling a Trac request ==59 == Profiling a Trac request 60 60 61 61 I've written a blog post on how I do basic profiling for Trac. It includes a simple script that I use to check single requests. [https://www.coderesort.com/u/simon/blog/2011/09/06/trac_profiling Read it @ my blog].
