We have recently upgraded from ccnet 1.3 to 1.5 and are seeing some interesting interval polling behavior that we don't quite understand. We have an interval trigger set in the .conf file for each project at 600 ( every 10 minutes). In cctray as I watch the detail column it reports the next build check. We have about 170 projects configured on a single build server. We are building against an Accurev source control server. The machine is Windows 2003.
What I see is that some projects have a fixed next build check time (let's say 10 minutes into the future), all the same time. Other projects have a different build check time that is the current time and it increments as time passes until it reaches the time of the other projects (10 minutes into the future) when they all then poll for modifications. I've also noticed that if a project builds it sets the next build time to the current time and increments until reaching the next build check for the other projects. This results in all of our projects polling our Accurev server all at the same time for modifications which results in quite a hit on our server. Seems it used to be that with 1.3 projects would be nicely staggered on their polling interval, that the interval timer was set to trigger 10 minutes after a modification check or build and didn't do this incremental syncing. Seems something is causing all of the projects to synchronize their next build check interval timer. Is this a setting somewhere? Something I can change to get back the staggered modification checking? Thanks for any input. Let me know if more info is needed to be clearer on this issue. Cindy
