Leandro Conde wrote: >> Once it's in the trac-post-commit-hook.py, it shouldn't need to interact with >> the subversion repo, so the size of the repo shouldn't matter. > > Yes, thats right ... I'm using the pre-commit-hook also, and it didn't > have the same problem. Seems it has something to do with the part that > are modifying the ticket (refs or closes) or maybe the mail sending > stuff ... I haven't been able to test that issue properly, though ... > >>> 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? > >> How many tickets do you have in your ticket database? > > It varies as it depends on the environment pointed at ... some of them > (the larger ones) have a couple hundreds tickets, but some others less > than a hundred. > I didn't see any delay variations depending on which environment I'm using ... > >> What database are you using (sqlite is the default)? > > Yes, I'm using SQLite ... Didn't have the time to change it since > install ... Though I'm planning to upgrade to PostreSQL on Windows > when I have a chance ...
You could see if sqlite is slow for whatever reason using it's command line client: -------------------- $ sqlite3 /path/to/trac.db SQLite version 3.3.6 Enter ".help" for instructions sqlite> select * from ticket where id=1; -------------------- If that command takes a long time to return (try for a few different values of 'id'), then you have your culprit, and you may want to accelerate the scheduled move to PostGRESQL... Other than that, I can't think of what could be hanging it up. Good luck, Matt --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
