Checkout acceptable time?

Continua CI Discussion
1

Hi

We have been using continua for over a year, and during this time one of the minor annoyances is the time it takes after we reset the cache on our repository.  This can take anything from 15 mins to 60 mins which seems very slow.  Our GIT repository is quite large at 300Mb, but even so these servers are locally connected

We have a build server, git (stash) server and a MSSQL database server all self host in Amazon each on dedicated instances all within the same subnet.  From continua we reference GIT using an internal URL so this should be nice and quick.  None of the servers seem to be overload and even when building the cache have very little activity showing on the CPU’s.

Does any know what ‘realistic’ time to reset the cache is for locally connected servers.

Were currently using  1.0.0.3158, we did try an a release of 1.5 last week but rolled back as we had issues with GIT connectivity

Thanks

Rob

2

Hi Rob thank you for your post.

We ran a quick test here (460mb, git repo running on a virtual machine, Continua server running in a virtual machine). We found ~ 45 seconds end to end (from the time of clicking the reset button until the repo showed as ‘ready’ on the repository screen).

To investigate further on this one we will require some additional information. Could you please send us (support@finalbuilder.com) a debug log of the repository reset (http://wiki.finalbuilder.com/display/continua/Debug+Logging). This should provide a better idea of what is taking the time.

In your email could you also provide further information on how often you reset the repo cache (and if you are resetting often why), further description of the AWS setup in use (eg instance type / AMI etc ?), and a further description of the issue you encountered with 1.5 (as we have made many performance improvements within this version which should help out users with larger repos).

Thanks again.

3

Hi Rob

We released an update today with a fix for Git Repositories, I think what you were seeing is the issue that we fixed (at least the symptoms sound the same).