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! :-)
> Also, I'm soliciting opinions on how concerned I should be about all the
> buzz re: repository corruption. I have 3 code bases. One is about 30,000
> files, one is about 10,000 files, and one is about 2000 files. (These are
> 'C' and C++ sources and headers, makefiles, perl scripts, etc, used to
> cross compile code for embedded cards in our printers).
To this, I dunno what to say. Subversion has been hosting its own
source code for years now, with (thank you, God) not a single case of
repository corruption. In all the previous scalability testing I've
performed, I've never been able to corrupt a Subversion repository.
And yet we get these reports...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 10 17:50:25 2003