Performance testing at a glance
Performance testing is used to provide an edge to application. Performance create a base line of effective use of application basis of time and response with effective use of available resource.
Questions Should ask first before Start a Performance testing.
1. Is my Test Configuration (duration / iteration setting) appropriate ?
2. Does my web application function properly under given load ?
3. How many Virtual Users were generated by Load Generator ?
4. Does the response times meet my target requirements ?
5. What was the slowest page on my web site ?
6. What was the Page that had longest download time ?
7. How many simultaneous users can my web application handle ?
8. What is the load generated by the virtual users on the network resources ?
9. What is the Performance of my Server and Database during the load test ?
Types of errors:
300 Multiple Choices
301 Moved Permanently
302 Found
303 See Other
304 Not Modified
305 Use Proxy
307 Temporary Redirect
400 Bad Request
401 Unauthorized
402 Payment Required
403 Forbidden
404 Not Found
405 Method Not Allowed
406 Not Acceptable
407 Proxy Authentication Required
408 Request Timeout
409 Conflict
410 Gone
411 Length Required
412 Precondition Failed
413 Request Entity Too Large
414 Request-URI Too Large
415 Unsupported Media Type
416 Requested Range Not Satisfiable
417 Expectation Failed
500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout
505 HTTP Version not supported
“connection errors”
Cannot find server or DNS Error.
cannot open the Internet site <Web address>. The operation timed out.
connection timed out.
“ Parameterization errors ”
Parametrization error may occur due to data constraints, wrong attribute and iterations.
"Response Validation Error Details"
Some time application return status response 200 but response may be wrong.
Reports:
User Details (Active Users vs Elapsed Time)
User Details should provide the number of Virtual Users active during the test run. You must verify the Active User Count at various intervals to see to it that the right load has been generated.
Hits per Second
Hits per Second helps you evaluate the amount of load Virtual Users generate, in terms of the number of requests to the server. More the number of hits, more is the load on the server. Http request can fora web page, an image, a style sheet, some JavaScript, a video file, etc.
Response time
Response Time is total time from once request made till completion.
Response time can be calculated based on queuing model M/M/1.
Formula is
R= S/1-U.
where R is response time
S is No of server
U is utilization
Response Time (mean value,Server response time, active user count)
From Response Time report it is possible to identify peaks in the response time over a period of time. Helps to identify issues when server is continuously loaded for long duration of time.
Response Time (per Transaction)
From this graph it is possible to identify peaks in the response time for transactions and then proceed to analyze the response times of individual pages.
Throughput:
through put is total amount of data. it is represented in Bit/ seconds or KB/seconds. Little's theory is used to calculate throughput i.e If a number of customers N are observed in a queue in a stable system and served in a period of time T and there are an equal number of arrivals A and leavers L, then, throughput is defined as X = A/T = L/T
Response time, the long-term average time spent resident in the queue and being served is R and R = N / X.
Menasce & Almeida derived formula for throughput is
Server throughput = No of real simultaneous user*[response time /(response time + Think Time)].
Server CPU vs Elapsed time
Application use the different kind of server. This report provide information about utilization of data base server and Application server( also others if used).
Comments
Post a Comment