Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Since no one directly commented on the problem, and Tony didn't comment, I'll add my not-totally-informed comments ;-) On 8/31/06, Johannes Kilian <Jo.Kilian at gmx.de> wrote: > Hi there, > > running an 2.0.41 CVSNT Server I have serious performance problems. > > I wonder whether a big "History"-file might be the reason? I believe the history file should be only appended, so it's size shouldn't have any impact on performance. > We have set up several repositories on the same server - and the hugest history file is about 23MB (the history files in the other repositories are much smaller (approx. 2-3MB each).) > > Now my questions: > 1.) Can a history file of 23MB cause performance problems within the repository it belongs to? 23MB seems a reasonable small file by any standards, so my guess would be "no, there must be another reason". > 2.) If there are several repositories on the same server: Can a huge history file in one repository influence the performance in the other repository? Not either. > 3.) How can I "clean up" a history file? Which information will be lost, when > renaming the current history file and start a new, empty one? Only information which you get by the 'cvs history' command, which is not usually very useful... BTW, may I ask what for are you using 'cvs history'? Cheers, Flávio