Re: Local checkout performance - cvs vs cvsup

2006-11-26 Thread Andrew Pantyukhin

On 11/25/06, Kris Kennaway [EMAIL PROTECTED] wrote:

On Sat, Nov 25, 2006 at 01:25:45AM +0300, Andrew Pantyukhin wrote:
 I use cvsup to maintain a full local copy of the CVS
 repo. I then use plain cvs to check out different branches
 of src from it. The problem is while cvsup only takes a
 minute each time I run it, cvs takes several times more.

 I run cvsup with -gs and cvs with -rR flags. Should
 I run a local cvsupd server or is there another way to
 speed things up? I only need the repo and the branches
 in read-only mode.

I guess cvs is slower because it needs to check for local diffs
before/while merging in changes.  By contrast cvsup will just blow
away any changes you have made.


Yay! I set up a local cvsupd and it now takes under
10 seconds to update any branch, as compared to
5-7 minutes cvs took.


There's probably not much you can do apart from not checking out full
trees unless you really need them.


You see, I use different branches in jails and on
boxes, so it makes sense to get the whole repo over
the net and sync to the branches locally.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Local checkout performance - cvs vs cvsup

2006-11-24 Thread Andrew Pantyukhin

I use cvsup to maintain a full local copy of the CVS
repo. I then use plain cvs to check out different branches
of src from it. The problem is while cvsup only takes a
minute each time I run it, cvs takes several times more.

I run cvsup with -gs and cvs with -rR flags. Should
I run a local cvsupd server or is there another way to
speed things up? I only need the repo and the branches
in read-only mode.

Thanks!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Local checkout performance - cvs vs cvsup

2006-11-24 Thread Kris Kennaway
On Sat, Nov 25, 2006 at 01:25:45AM +0300, Andrew Pantyukhin wrote:
 I use cvsup to maintain a full local copy of the CVS
 repo. I then use plain cvs to check out different branches
 of src from it. The problem is while cvsup only takes a
 minute each time I run it, cvs takes several times more.
 
 I run cvsup with -gs and cvs with -rR flags. Should
 I run a local cvsupd server or is there another way to
 speed things up? I only need the repo and the branches
 in read-only mode.

I guess cvs is slower because it needs to check for local diffs
before/while merging in changes.  By contrast cvsup will just blow
away any changes you have made.

There's probably not much you can do apart from not checking out full
trees unless you really need them.

Kris


pgpcR9DnweYst.pgp
Description: PGP signature


CVS vs CVSup

2004-06-07 Thread Joshua Lewis
What is the difference between CVS and CVSup?


Thank you,
Joshua Lewis

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: CVS vs CVSup

2004-06-07 Thread Chuck Swiger
Joshua Lewis wrote:
What is the difference between CVS and CVSup?
The cvsup manpage quite reasonably provides a description:
DESCRIPTION
 CVSup is a software package for distributing and updating collections of
 files across a network.  The name CVSup refers to the package as a whole.
 It consists of a client program, cvsup, and a server program, cvsupd.
[ ... ]
 Unlike more traditional network distribution packages, such as rdist and
 sup, CVSup has specific optimizations for distributing CVS repositories.
 CVSup takes advantage of the properties of CVS repositories and the files
 they contain (in particular, RCS files), enabling it to perform updates
 much faster than traditional systems.
:-)  CVS is a software version management system, CVSup is a distribution 
mechanism which understands CVS well.

--
-Chuck
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]