Best policy for CVS repository history file

[sandy_liss]

Hi Thomas,

I wondered whether you - or any other users - could offer any advice on
the best policy for the CVS repository history file.

At present, our repository history file goes back 5 years or more and
is about 200 Mbytes in size. Presumably the larger it gets, the slower
any CVS operations on it become, eg SmartCVS Remote Refresh.

On the other hand, if we prune the oldest entries, then we will be
losing some old information (although AFAIK all of the really important
information - commits, tags etc - is stored in the archive files
themselves).

Do you have any advice? What effect does history file size have on
performance?

And if we do prune the history file, which of the more advanced
SmartCVS operations (eg List Transactions, Compare Repository Files)
would be affected?

Thanks
Sandy






------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/smartcvs/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/smartcvs/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:smartcvs-digest@...
    mailto:smartcvs-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    smartcvs-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

[SyntEvo Support-2]

Hi Sandy,

I can't say that I know the *best* policy to handle the CVSROOT/history file.
But we (small team with nearly latest working copies) delete the history file
from time to time, especially after having deleted accidentally added (.class)
files directly in the repository.

> What effect does history file size have on performance?

I guess, it depends on different issues (e.g. size of the project, size of the
history file, the network and server speed). To test it for your project, edit
the file log4j.properties and add following line

 log4j.category.sm.command.cvs=DEBUG

to see the command execution times.

--
Best regards,
Thomas Singer
_____________
SyntEvo GmbH
www.syntevo.com


"sandy_liss" <sandy.kellagher@...> wrote:

> Hi Thomas,
>
> I wondered whether you - or any other users - could offer any advice on
> the best policy for the CVS repository history file.
>
> At present, our repository history file goes back 5 years or more and
> is about 200 Mbytes in size. Presumably the larger it gets, the slower
> any CVS operations on it become, eg SmartCVS Remote Refresh.
>
> On the other hand, if we prune the oldest entries, then we will be
> losing some old information (although AFAIK all of the really important
> information - commits, tags etc - is stored in the archive files
> themselves).
>
> Do you have any advice? What effect does history file size have on
> performance?
>
> And if we do prune the history file, which of the more advanced
> SmartCVS operations (eg List Transactions, Compare Repository Files)
> would be affected?
>
> Thanks
> Sandy
>
>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/smartcvs/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/smartcvs/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:smartcvs-digest@...
    mailto:smartcvs-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    smartcvs-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/