Topic: Stress Testing and Performance Testing

Message

Stress Testing:

The purpose of stress testing is to find defects of the system capacity
of handling large numbers of transactions during peak periods. For
example, a script might require users to login and proceed with their
daily activities while, at the same time, requiring that a series of workstations emulating a large number of other systems are running recorded scripts that add, update, or delete from the database.

Performance Testing:

System performance is generally assessed in terms of response time and
throughput rates under differing processing and configuration
conditions. To attack the performance problems, there are several
questions should be asked first:

How much application logic should be remotely executed?
	How much updating should be done to the database server over the network from the client workstation?
	How much data should be sent to each in each transaction?

According to Hamilton [10], the performance problems are most often the
result of the client or server being configured inappropriately.

The best strategy for improving client-sever performance is a
three-step process [11]. First, execute controlled performance tests
that collect the data about volume, stress, and loading tests. Second,
analyze the collected data. Third, examine and tune the database
queries and, if necessary, provide temporary data storage on the client while the application is executing.

Edited by moderator - 05May2007 at 2:11am

Author	Message
vidhya Senior Member Joined: 24Mar2007 Online Status: Offline Posts: 114	Topic: Stress Testing and Performance Testing Posted: 26Mar2007 at 8:51pm
	Stress Testing: The purpose of stress testing is to find defects of the system capacity of handling large numbers of transactions during peak periods. For example, a script might require users to login and proceed with their daily activities while, at the same time, requiring that a series of workstations emulating a large number of other systems are running recorded scripts that add, update, or delete from the database. Performance Testing: System performance is generally assessed in terms of response time and throughput rates under differing processing and configuration conditions. To attack the performance problems, there are several questions should be asked first: How much application logic should be remotely executed? How much updating should be done to the database server over the network from the client workstation? How much data should be sent to each in each transaction? According to Hamilton [10], the performance problems are most often the result of the client or server being configured inappropriately. The best strategy for improving client-sever performance is a three-step process [11]. First, execute controlled performance tests that collect the data about volume, stress, and loading tests. Second, analyze the collected data. Third, examine and tune the database queries and, if necessary, provide temporary data storage on the client while the application is executing. Edited by moderator - 05May2007 at 2:11am Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Software Testing @ OneStopTesting : Versioning & Configuration Management @ OneStopTesting