April 30, 2002 at 12:09 am
Hi,
My manager has asked me to come up with a plan for load/stress testing. As part of our system test we have to do this, before shipping the application to our client.
This is the first time, I would be doing such an activity. I am looking for some help in this aspect like where to start and what to look for.
Our database is on SQL Server 2K. Load/stress test has to be done on the database (ours being a database oriented application).
R any tools/templates are available.
Thanks & Regards,
Mitra
April 30, 2002 at 5:20 am
Most of the tools I have seen either are for hardware or capture queries to play back to the server which profiler can do. Best I have ever done to test was to find a box with minimal specs and perform a checklist of user tasks that would be normal, then get someone who knows nothing about the systems workings and just tell them figure it out. Next I would supply a list of things to accomplish and all the while have profiler catching the traffic. Then using it to perform a playback you can simulate more users doing the same things. The reason to use a box with minimal specs is to make small bugs have a greater impact and show up better and large bugs almost become blatantly easy to find.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 30, 2002 at 9:09 am
There are tools such as Mercury Interactive's WinRunner and LoadRunner which can stress test an application, but they aren't the only ones in the business. Do you need to test the complete application (ensuring there are no bottlenecks in any of the components) or just the database back-end?
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
April 30, 2002 at 10:20 am
We used to use a tool from Quest Software. It had a high learning curve and takes time to use. They are alos Expensive $$$. You can rent them, but they will also be expensive.
I'd create scripts that mimic what your app will do and write some loops around them. Then have as many desktops as you can find execute these and monitor the server. That is the best way on the cheap.
MS has some free tools, like the Web Application Stress Tool that will help you. There is one for SQL I believe, but I haven't use it.
Steve Jones
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply