Yes, I'm just pointing out that CVS works fine on a large project. 18M source is a large project on my world. Bob has obviously slipped into some future time dimension on a distant planet, thus the 1.8G use. Welcome to the twilight zone, you will be programming in this cubical :) I recall the full cvs repository for this sdcc project at around 60M. Maybe your cvs delta history is overflowing with a bunch of binary bitmaps? If the actual source tree is of reasonable size, maybe you need to purge some history? Start a fresh repository? If your actual source is > 100M you need to find your way out of the twilight zone :) On Thu, Aug 14, 2003 at 09:54:53PM -0500, Wayne Johnson wrote: > > It depends on the number of files and the updates in those files, as well > as the server horsepower. > > Karl Bongers said: > >> On Wed, Aug 13, 2003 at 04:29:24PM -0500, Bob Tanner wrote: > >> > When your cvs repository gets large enough that a cvs update -dP > >> takes 15mins, and cvs commit at just as long, what do you do? > > > > A cvs checkout on a 18M project(sdcc) on sourceforge just took > > about 1 minute. Afterwards a cvs update took about 5 seconds. > > How large can your repository be? > > _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list