Re: Idea for reducing disk IO on tagging operations

[Tony Aiuto]

>Tagging in particular is slow and I don't think cpu or ram is the
>issue (it is a dual xeon with 3GB of RAM).
>...

I'll be shot as a heretic, but the real solution is that tags don't
belong in the ,v files in the first place.  IMO the only useful purpose
of tags is to snapshot the entire code base in some way so that you can
roll back to it (or diff against it).   Tagging individual files doesn't
to anything to help you understand their relation over time to the rest
of the code base.

The entire system tag could be accomplished in O(# files) time (rather
than O(repository disk size) by simply creating a manifest of each
file in the repository and its version at the time of the snapshot.
The snapshot/manifests become entities in their own right, so you should
be able to do things like list available snapshots, see when they
were created, add meta information to the snapshot ...

-Tony Aiuto