[cvsnt] Re: Repository TAG behavior

[Randy McCharles]

I suspect putting the binaries in a separate repository will just move the problem. You won't experience time-outs on the original repository, but will on the new one. It would be an interesting experiment. If time-outs continue on the original repository. i.e. if the original is being tagged while another client is committing or tagging the binary repository, then this would imply that the lock-server is being tied up and not the actual files.

Randy McCharles

SMART Technologies Inc.

Senior Software Developer

Tel. 403.802.3347  Fax 403.229.2531
randymccharles at smarttech.com
http://www.smarttech.com

Bringing people and ideas together.(tm)



-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Gerhard Fiedler
Sent: Tuesday, February 07, 2006 5:10 AM
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Re: Repository TAG behavior


Randy McCharles wrote:

> We also have a lot of binaries (as many binaries as text files). Having
> dealt with this problem for a while I have concluded that it is
> convenient, but not essential, to keep all binaries in source control.
> What I did was start with the largest RCS files and systematically moved
> them to a flat archive system. I use a naming scheme that combines the
> binary file name and its version. The majority of binaries are small and
> I left under source-control. Every few months I look for the largest
> files again to see if they should be removed. 

Could it be an option to keep the binaries in a separate repository? Would
that help, given that they are still handled by the same (lock)server
processes?

Gerhard
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt