On Fri, Oct 10, 2003 at 10:49:01AM -0500, C. Michael Pilato wrote:
> tnoell@lexmark.com writes:
>
> > So, I was wondering if you and the folks doing scalability testing this
> > week are planning on concurrent user scalability testing. i.e., what
> > happens when 120 people (or 500) are banging in lots of commits
> > "simultaneously". I am being asked if it will hold up, and I don't know
> > what to say, yet.
>
> Yes, part of our testing will involve concurrency. I should note,
> though, that if all 120 of your developers are committing at the same
> time -- well, you might consider blanket pay raises for the
> Engineering department! :-)
>
One potential issue is the "up to date" check at commit time. If your
120 people are banging in lots of commits, there is a potential for some
amount of starvation; if you're never up to date, you can never commit.
I think that in practice this is reasonably unlikely; you'd have to
be crazy to have 120 people working on the same files at the same time.
However, the bubble-up nature of directory versioning may exacerbate
this problem.
It would certainly be interesting to hear how well the *model* scales,
as opposed to the *software*.
For Very Large Software Projects, features like ClearCase's "winking"
of derived objects and it's notion of "LATEST" configurations may
justify the enormous software and management expense.
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 10 19:54:15 2003