On Fri, 2006-03-17 at 20:06 +0100, Christian Boos wrote: > Russ Brown wrote: > > On Thu, 2006-03-16 at 14:16 -0600, Russ Brown wrote: > > > >>> I believe the command is: > >>> $ trac-admin resync /your/trac/env > >>> > >>> > >> Thanks! I knew I remembered seeing something like this before. > >> > >> OK, I've run it but unfortunately its not cured the problem. > >> > >> To investigate a little further I've played a little with the timeline > >> filters. If I show everything but Repository checkins it is very fast, > >> but if I show only checkins it is very slow. I'm only showing 7 days of > >> history too, and this only used to take a couple of seconds at the most. > >> Now it takes something like 39 seconds. > > What would be very valuable here is to know what was the last revision > for which the timeline was 'fast'. > You could setup a test server on the same repos that is showing the pb, > then do a dichotomic search to find the culprit rev. >
Due to the wonders of bash command line history, I can report that the previous revision we were running against was 2651. Are there any problems with running a version of the code that is older than the trac database it is being run against? If not I can try switching back to an older rev and seeing if that resolves the problem. As you say I can then experiment with the revision until I find the one at which things slow down at. Thanks. -- Russ _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
