info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tags and performance.


From: Noel L Yap
Subject: Re: Tags and performance.
Date: Tue, 17 Oct 2000 14:31:14 -0400

I think this cost is marginal.  CVS performance is more dependent on the number
of files in the repo than the size of the archive files.  This is 'cos a file
open/close is much more expensive than parsing.

Noel




address@hidden on 2000.10.17 14:03:39

To:   address@hidden
cc:   address@hidden (bcc: Noel L Yap)
Subject:  Re: Tags and performance.




The more tags that you have on a file, the longer it takes cvs
to actually parse the file whenever cvs looks at it in the repository.
Your not going to run into problems persay, but you will notice
a gradual increase in time to access files in the repository....

donald
On Tue, Oct 17, 2000 at 01:19:48PM -0400, Tommy McNeese wrote:
>
> I was wondering if anyone has ever experience and kind of performance problems
> when dealing, say hundreds of tags on a file. That is, our developement,
> testing and release cycle is very active. If we tag all of our test builds,
the
> number of tags could grow considerable. Are we going to run into problems with
> many many tags?
>
>
> Thanks,
> Tommy
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs

_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs





This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]