[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Stress Test Scripts?/Utils?

From: Samay <getafix123_at_hotmail.com>
Date: 2005-04-13 19:03:25 CEST

I intend to test with 10-12 simultaneous SVN tasks. Server is on a GigE
connection, and all test clients are on local network only. my current test
scripts are similar to
"time svn co -q https://svn.example.com/repos/trunk >> StatCO.txt"
"time svn log -q https://svn.example.com/repos/trunk >> StatsLog.txt"

any other stats that can/should be collected? Any other operations that can
be reasonably stress tested. Yup, CheckIns, is tricky, unless i just test
them with 'svn co, svn update, svn add, svn ci, svn log' in that order!
Collecting Network utlisation, and traffic to Kerberos KDC' etc as well.

thanks Kevin.


----- Original Message -----
From: Kevin Greiner
To: Samay
Cc: users@subversion.tigris.org
Sent: Thursday, April 14, 2005 2:36 AM
Subject: Re: Stress Test Scripts?/Utils?

How many silmultaneous connections do you intend to test?

Since svn is cmd line, you could just write some scripts. The hardest part
may be simulating checkins of various numbers of modified files.

svn co svn://svnserver/path/to/repos/app
svn log svn://svnserver/path/to/repos/app

On 4/13/05, Samay <getafix123@hotmail.com> wrote:

We would like to stress test our Subversion Installation to see how it
performs under heavy load (essentially many simultaneous checkouts, logs
requests, with our test repos ~few gigs).

We generally use OpenSTA for web application stress testing, but I don't
think its a valid tool for this case!

any pointers, helps, past experience, etc .. much appreciated.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 13 19:11:24 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.