Hi Trac people, I've been using Trac for a while now, and I'm beginning to have a serious problem.
I'm using Trac 10.1, I didn't been able to upgrade yet, due to lack of spare time ... too much work and pressure to finish some of it really NOW. So, I asking this in a little time I have for breakfast ... If the solution is to upgrade, I will proceed with that ... but, since the post commit hook is external to Trac, seems that it has nothing to do with this problem. The setup that I've choosed is one single svn repository with multiple tracs 'seeing' portions of it. I have Trac running on a Windows 2000 server with Apache 2.0 and SVN 1.4.1 and Python 2.4. I'm using the mod_python way. And I'm using the trac-post-commit-hook.py downloaded form the Trac wiki some weeks ago ... without changes. The SVN repository has grown a bit now, it has nearly 4000 revisions, made mostly by importing stuff from another 'version control system' (the one from M$). Now I'm having extremely large commit times (worst case is greater than 30 secs, and best case is no less than 5 secs), and while waiting for the SVN client to return from a commit, I look into the server's process list, and I see python.exe taking 10% of CPU and if I see the command line, I see that it is executing the trac-post-commit-hook.py. So, is this a known problem? It has any solution? Is there any other hook script to try out? Upgrading has any to do with it? I didn't find mention of this problem in this mailing list ... Please, any help would be appreciated ... Best regards, Leandro. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
