Topic: Performance testing

Message

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, 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.
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.

Performance testing is the process of determining the speed or effectiveness of 
a computer, network, software program or device. This process can involve 
quantitative tests done in a lab, such as measuring the response time or the 
number of MIPS (millions of instructions per second) at which a system 
functions. Qualitative attributes such as reliability, scalability and 
interoperability may also be evaluated. Performance testing is often done in 
conjunction with stress testing.

Performance testing can verify that a system meets the specifications claimed 
by its manufacturer or vendor. The process can compare two or more devices or 
programs in terms of parameters such as speed, data transfer rate, bandwidth, 
throughput, efficiency or reliability. 

Performance testing can also be used as a diagnostic aid in locating 
communications bottlenecks. Often a system will work much better if a problem is 
resolved at a single point or in a single component. For example, even the 
fastest computer will function poorly on today's Web if the connection occurs at 
only 40 to 50 Kbps (kilobits per second). 
Slow data transfer rate may be inherent in hardware but can also result from 
software-related problems, such as: 
Too many applications running at the same time
A corrupted file in a Web browser
A security exploit
Heavy-handed antivirus software
The existence of active malware on the hard disk. 
Effective performance testing can quickly identify the nature or location of a 
software-related performance problem.

Edited by Mithi25 - 09Jul2009 at 3:28am

Author	Message
Mithi25 Senior Member Joined: 23Jun2009 Online Status: Offline Posts: 288	Topic: Performance testing Posted: 09Jul2009 at 3:20am
	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, 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. 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. Performance testing is the process of determining the speed or effectiveness of a computer, network, software program or device. This process can involve quantitative tests done in a lab, such as measuring the response time or the number of MIPS (millions of instructions per second) at which a system functions. Qualitative attributes such as reliability, scalability and interoperability may also be evaluated. Performance testing is often done in conjunction with stress testing. Performance testing can verify that a system meets the specifications claimed by its manufacturer or vendor. The process can compare two or more devices or programs in terms of parameters such as speed, data transfer rate, bandwidth, throughput, efficiency or reliability. Performance testing can also be used as a diagnostic aid in locating communications bottlenecks. Often a system will work much better if a problem is resolved at a single point or in a single component. For example, even the fastest computer will function poorly on today's Web if the connection occurs at only 40 to 50 Kbps (kilobits per second). Slow data transfer rate may be inherent in hardware but can also result from software-related problems, such as: Too many applications running at the same time A corrupted file in a Web browser A security exploit Heavy-handed antivirus software The existence of active malware on the hard disk. Effective performance testing can quickly identify the nature or location of a software-related performance problem. Edited by Mithi25 - 09Jul2009 at 3:28am
	Send Unlimited FREE SMS to Any Mobile Anywhere in INDIA, Click Here Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Types Of Software Testing @ OneStopTesting : Performance & Load Testing @ OneStopTesting