Trac hangs with large subversion repositories.

[anonymous]

We have a repository which has been migrated from CVS. As a result there are several hundred files, with about 15000 comitted changesets. With the version of trac that we were using (0.9.6) we could still use most of Trac, i.e. the wiki, tickets and milestons. However the browse source would take so long to run that it would timeout the browser and lock the database for a few minutes. I upgraded to 0.11dev and now it wont even load the Trac page at all. Turning on logging shows that for some reason Trac seems to cache every single change on every file at startup:

… Lots of identical messagse to the next one with differing change sets … Trac[cache] DEBUG: Caching node change in [9661]: (u'filename omitted for privacy', etc)

Is there any workaround for this?

[Matthew Good]

Trac caches information about the repository in its database. If there are lots of changesets this process will take a while. Try running "trac-admin /path/to/your/project resync" and let it run until completion. When you use Trac again the cache will be up to date and it will only need to check for new revisions, which is quite fast. If that fixes this please close the ticket as worksforme.

[wross@…]

I'm not the person who opened this issue, but I can verify that the proposed solution works. I had a freshly-imported SVN repository with ~18000 changes. Trac went away for >12 hours when asked to display the "Timeline" or "Browse Source" screens. Running resync fixed the problem completely. It's quite fast now.

[Christian Boos]

Well, 12 hours … 2.4 changesets per second. Must have been big changesets ;)

Thanks for the feedback!