Changes between Version 7 and Version 8 of TracPerformance

Timestamp:

Sep 9, 2009, 3:19:36 PM (15 years ago)

Author:

Christian Boos

Comment:

move resync failure item from #Unsorted to #Log

TracPerformance

@@ -50 +50 @@
  - look for INFO messages: ''Reloading environment due to configuration change'' [[br]]
    if you find lots of such lines, or even worse, if they appear systematically, then chances are that you're using a plugin which does systematic updates to the configuration file ([TracIni trac.ini]), and this will in turn trigger a full environment reload at the next request. That can slow down the performance a lot, to the level of TracCgi. See ticket:7490#comment:102 and follow-up.
+ - look for INFO messages like repos ''rev [321] != cached rev [123]'' (other revision numbers for you, of course) [[br]]
+   if you find such lines ''and the `cached rev` value doesn't change'', this corresponds to a repository resync failure which results in a resync attempt for every request (see ticket:7490#comment:36); often due to the "prohibited" MySQL/MyISAM combination (#8067)
+
 
 == Unsorted ==
  
- - repository resync failure which results in a resync attempt for every request - easy to spot in the Trac log (see ticket:7490#comment:36); often due to the "prohibited" MySQL/MyISAM combination (#8067)
- - there was a bug up to 0.11.4 which could cause 100% cpu usage on some platforms (#7785, fixed in 0.11.5)
+ - 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)
  - some plugins seem to have a high impact on the performance (read ["TracDev/Performance/0.11.5#customizationsandplugins"])
  - a mis-configured or simply slow mail server make Trac appear very slow (#3220 and numerous others)