On Saturday, June 1, 2013 3:39:10 AM UTC-7, W. Martin Borgert wrote:

> Hi, 
>
> I'm trying to integrate a Git repository into Trac. For testing I 
> chose the Linux kernel (~375000 commits, ~1.3 GB). I first tried 
> without any special settings in trac.conf. Unfortunately the "Browse 
> Source" view was unusable slow. Than I tried the setting with: 
>
> [git] 
> cached_repository = true 
> persistent_cache = true 
>
> This time the synchronisation took ~36 hours until all revisions were 
> in the database, and everything seems to be faster, but still so slow, 
> that I cannot foist this on my colleagues. 
>
> I wonder, whether I have to tune something to make it work? Some more 
> Trac parameters? Or PostgreSQL? The repository itself is OK: A quick 
> test with the Gitk showed that the access can be very fast. 
>
> My setup: Debian wheezy+jessie mix 
> Trac 1.0.1 
> Git (and Gitk) 1.7.10.4 
> PostgreSQL 9.1 
> Apache 2.2 
> Mod-WSGI 3.3 
> Python 2.7.5 
>
> Thanks in advance! 
>
> Cheers 
>

I just started working with the Git connector component as well, and 
noticed on the Git documentation page [1]: "Please note that we're still 
considering the level of performance to be sub-optimal, so it might not 
work for you. Small to medium sized repositories should be handled 
reasonably well, however."

I imagine you already have this, but did you repository_sync_per_request to 
an empty value and instead setup a post-receive hook to sync changes?:

[trac]
repository_sync_per_request = 

[1] http://trac.edgewall.org/wiki/TracGit 

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to