Ive created a program that needs to commit to repositories. I'm using slikSvn. It seems that the very first commit I make is very slow (20 sec) but every other commit is much faster more like 1 sec. Is there some kind of connection to slikSvn I can make when I first load my program to avoid this 20 sec commit? Please let me know what additional information you need. thanks
A:
The first commit has to make a copy of all the files.
Subsequent commits only need to copy the changes.
Other than a faster link - or somehow send the initial copies by some other faster means (sneakernet) there isn't much you can do.
Martin Beckett
2010-08-04 15:19:28
but both commits are not on the same folder, and it dosen't matter which folder I do first.
hrh
2010-08-04 15:21:49
does this make a difference?
hrh
2010-08-04 15:44:21
Also this is not the first commit ever, just first commit since the program has been open.
hrh
2010-08-04 15:48:38
A:
Maybe that delay is caused by the clients authentification with the server. (Does it happen with every first command or just with every first commit?)
If it is authentification-related then you could probably just send a small request to the server when your program loads like "svn list -r0 REP_URL" (this would be for subversion, but I'm sure there is a similar command in slikSvn)
El Chupacabra
2010-08-05 09:29:29
hrh
2010-08-11 19:37:29
running list during load did not help. However I think this is the right idea, I just think I need to choose a different command.
hrh
2010-08-18 14:25:18
The idea behind "list -r0" was to use a command that doesn't create any output (since it lists revision 0 which should be empty), thus lowering bandwith usage and CPU-time on the server...but maybe you need some output to trigger the delay.
El Chupacabra
2010-08-20 09:55:21