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.
Matt Schuckmann wrote: > > Um that's not what I've seen and reported. I've seen operations as > simple as checking to see if a tag exists take as long as 30 or 40 min > on a large binary ,v file. If memory servers, it appeared that it was > loading the entire file into memory and the server ran out of RAM and > started thrashing on the disk. > Only cvs log reads the entire file (even that is optimised in 2.5.02 to use a lot less memory) - something like tags will only read the file header, which is going to be very little memory. eg: $ ls -lh /usr/local/cvs/cvsnt/configure,v -r--r--r-- 1 nobody cvs 6.9M 2005-10-02 16:02 /usr/local/cvs/cvsnt/configure,v $ cvs -ttt status configure 2>&1 | grep "End Rcs" 16:04:06: -> End Rcs buffer size = 128K $ cvs -ttt log configure 2>&1 | grep "End Rcs" 16:06:26: -> End Rcs buffer size = 2048K $ cvs -ttt diff -r 1.1 configure 2>&1 | grep "End Rcs" 16:07:54: -> End Rcs buffer size = 128K 16:07:54: -> End Rcs buffer size = 2048K 16:07:55: -> End Rcs buffer size = 2048K Tony