I have lots of projects (all small projects but more than 20). All repositories have the default polling frequency (60 seconds), but it totally breaks down the server. I recommend to get the changesets of at most 5 repositories at the same time. If there are more, just queue them because it’s better to have a delay than to have the server go down.
Agreed, will look into it. At the moment it fires off the checking asynchronously, but doesn’t limit the number of threads, will need to rework the code a fair bit to achieve this but it should be doable.
I have set all repositories to 5 minutes now, seems much more stable. It was git for windows taking all the CPU (and more than 20 instances of that is killing). The Continua CI service wasn’t taking much CPU, it really was git.
Is there an ETA on this feature? Every time my server has to reboot, it becomes unusable because all repositories are being checked all at once. I cannot log in or take over the machine because it is completely unresponsive (taking 100% CPU). I have added a batch file on the desktop to kill all git instances, but in order to run that I need to log in which also takes at least 10 minutes.
Sorry, this fell through the cracks, will discuss with the team tomorrow. I guess the the question is though, how many should we allow to run at a time.
I think 5 is a good number. The rest should be in the queue, but with 5 it will at least keep my system accessible.
Hi Geert
Please try this build :
http://downloads.finalbuilder.com/downloads/continua/1.5/ContinuaCI.Server.Setup_x64_1.5.0.305.exe
http://downloads.finalbuilder.com/downloads/continua/1.5/ContinuaCI.Agent.Setup_x64_1.5.0.305.exe
http://downloads.finalbuilder.com/downloads/continua/1.5/ContinuaCI.Server.Setup_1.5.0.305.exe
http://downloads.finalbuilder.com/downloads/continua/1.5/ContinuaCI.Agent.Setup_1.5.0.305.exe
This build includes a new Server Property - Server.RepoMonitor.MaxCheckers - which defaults to 5. We also add a delay during startup so that the repositories do not all start checking immediately. Another thing we did was to change the setting of the last checked property to when it finished checking, this results in a more staggered checking of repos. On our main server, which has 20+ repos, I only see 2 or 3 checking at a time after this change.
This is awesome. I just reset all the checks from 5 minutes to 60 seconds on all my repositories. So far so good, it even worked while restarting the server (normally it would be unresponsive from the beginning keeping me out of the loop). Great work, thanks!
fyi: just counted, I have 39 projects. Is there a way to get such statistics without counting manually?