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.
Bo Berglund sez: > On Tue, 13 Jun 2006 14:29:28 -0400, John Hardin <jhardin at epicor.com> > wrote: > > >Operations (commit, update, diff) involving large individual files > >(larger than about 800KB) experience > > This is not a particularly large file... > If you had said 800 Mb I would have agreed tit is s large file, but > 800 kb is nothing, really. Wow. You regularly deal with 800kB+ text files? > The problem is not connected with the file size for this size anyway. That's the only indicator I have. The problem becomes noticeable at around 800kB and gets unbearable at over 1.5MB, and non-cvsNT clients are not seeing the delays. See my other post with trace and timing data (which is in the moderator queue at the moment). > (Or if the file is a binary file Nope. XML Text. > and you have already stored many > revisions, then the RCS file in the repository may be very large and > this will make CVSNT run into performance issues like disk swapping etc > depending on available RAM... We don't use cvsNT on the server side. Were you assuming I was talking about server delays? -- John Hardin KA7OHZ Senior Applications Developer, RetailCRM Development web: http://www.epicor.com voice: (425) 672-1304 fax: (425) 672-0192 email: <jhardin at epicor.com> EPICOR|CRS Retail Solutions Division 3400 188th Street SW, Suite 185 Lynnwood, WA 98037 ----------------------------------------------------------------------- The first time I saw a bagpipe, I thought the player was torturing an octopus. I was amazed they could scream so loudly. ----------------------------------------------------------------------- This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses.