[cvsnt] Out of memory

Lehman, Curtis CLehman at carrieraccess.com
Thu Oct 6 21:08:44 BST 2005

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.


Sorry about the slow response, I was out on training the last two days. 

The file that is causing concern for me is a text routing file, it's not
binary like I first thought, that is created by the compiler for our FPGA
development. The original file size is 10MB and it almost totally changes
between each release. We are on version 18 on the main trunk of the file.
It's already 170MB on the server. 

The server is a dual 3.0 GHz xeon processor with 2MB of cache on each
processor and 2 GB of ram. It's a screaming machine. It has a gigabit
connection to the network.

Any other suggestion on how to maintain such a file is greatly welcome.


-----Original Message-----
From: Bo Berglund [mailto:bo.berglund at telia.com]
Sent: Monday, October 03, 2005 11:42 PM
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: Re: [cvsnt] Out of memory

On Mon, 3 Oct 2005 16:43:16 -0600, "Lehman, Curtis"
<CLehman at carrieraccess.com> wrote:

>Do you have any suggestion on how to mitigate or fix this issue? I am
>worried my system will run into this eventually since we are revision
>controlling binary files (-kb) that change a lot. I was wondering if I
>change the way CVS saved the file, maybe by switching to the -KB for delta
>binary's? Can I make this change on existing binary files and still retain
>the ability to pull early versions that were under the -kb option? 
>Any other suggestions on what we could do to prevent this from happening?

As far as I know there are just these few things you can do:

1) As you suggested change to binary deltas. I have never tried this
myself so I don't know all ramifications, but one is a complete break
with standard RCS file format so you cannot go back to a non-CVSNT
server on these repositories. I also do not think that this will
affect the existing data, only new additions to the file.
If the file changes a lot inside for your actions then binary deltas
might not even help...

2) Get a *lot* more RAM for your server

3) Use the cvs admin command to get rid of the non-relevant revisions
in the file. This is a *very* slow and painstaking process on big RCS
files and the server must be able to work with the file in the first

How big was the RCS file in your repository when you checked?
And how much physical RAM is the server equippped with?

(Bo Berglund, developer in Sweden)
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook