[cvsnt] Out of memory

[Lehman, Curtis]

Yaa, I think that's what we are going to have to do. We have to keep the
file on revision control because we need it for the debugger to work. This
file, even though compiler generated, is not reproducible. Every time we
compile the code, this file changes, even without any code changes because
there is a random number generator in the program that creates different
numbers. 

Thanks for the help and time,
Curt

-----Original Message-----
From: Bo Berglund [mailto:bo.berglund at telia.com]
Sent: Thursday, October 06, 2005 2:41 PM
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Out of memory


On Thu, 6 Oct 2005 14:08:44 -0600, "Lehman, Curtis"
<CLehman at carrieraccess.com> wrote:

>Bo,
>
>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.
>

Looks like you really have a good server there!
So this means that the problem is not RAM size either. Only remaining
is the pure size issue. Tony maintains that big files are not a
problem since only the deltas are stored and CVSNT can quickly access
HEAD at least.

But I understand your problem now and it is similar to the slightly
less problem we have with embedded microcontroller development. The
final result of a compile is a text file that is really the image of a
binary program in hex format. So it too changes almost completely
between rounds. We decided not to store this file in CVS because it
can be exactly created off of the stored sources (we did some tests
and the result was a 100% binary compare).
In your case, if you want to still save the file in CVS I would make a
cut somewhere and make a copy of the RCS file under another name and
then start anew by using the admin command and delete the first 17
revisions from the file. The renamed copy will serve as backup. Then
at least you can continue a while with a faster module...


/Bo
(Bo Berglund, developer in Sweden)
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt