RE: need a server-busting test case

[Bulgrien, Kevin]

> Is there something I can do with CVS that will demonstrate high I/O
> and/or memory requirements?  I have access to a repository with ~43K
> files.  Would it suffice to have some tagging, checkouts and commits
> going (almost) concurrently?

Do concurrent cvs update -r1.1 (or equivalent early tag) on multiple
sets of files, each of which contain a very large file with a lot of
history.  That just from my experiences with controlling "large" files
on an old hardware platform.  See the mailing list thread of January
2008:

  Large file actual performance report; cvs use of ,v header is
  sometimes non-optimal.

The thread has some numbers.  Chances are your virtual system will be
a lot more beefy than my poor server, so the metrics will have to be
scaled to suit.

And that probably isn't worth 2 cents... but you can have it if you
want.

Kevin

This email message is for the sole use of the intended recipient(s) and may 
contain General Dynamics SATCOM Technologies confidential or privileged 
information.  Any unauthorized review, use, disclosure or distribution is 
prohibited.  If you are not an intended recipient, please contact the sender by 
reply email and destroy all copies of the original message.