Server Capacity Testing
The worst case scenario for any E-commerce business is having so many users that your web server crashes. Lack of capacity planning can result in untold losses, inconvenience and loss of corporate reputation. Lack of user confidence, brand value and Google Adword hits further increase these losses.
ForLinux can check your server capacity and produce a personalised report detailing the findings of the test and give recommendations to ensure you maximise your future sales potentials. By simulating the HTTP requests generated by hundreds of simultaneous users, we can test your web server’s performance under normal and excessive load to ensure that critical information and services are available at speeds your end-users expect.
Key Benefits
• Realistic functional tests. Realistic server loading.
• Load your server with 50+, 100+, 500+ LoadTest user sessions.
• Functional tests can play back ANY browser sequences.
• LoadTest scenarios use any functional test scripts.
• LoadTest playbacks are fully “stateful,” maintaining user context.
• Reliable and revealing LoadTest Reports.
• Tests behave as real users. Your servers see actual user behaviour, not approximations.
Metrics logged by the Stress Test
• Transactions – The number of server hits. For example, 25 simulated users each hit the server 10 times , a total of 250 transactions. It is possible for the number of transactions to exceed the number of hits that were scheduled.
• Availability - This is the percentage of socket connections successfully handled by the server. It is the result of socket failures (including timeouts) divided by the sum of all connection attempts. This number does not include 400 and 500 level server errors which are recorded in “Failed transactions” described below.
• Response time – The average time it took to respond to each simulated user’s request.
• Transaction rate – The average number of transactions the server was able to handle per second, in a nutshell: transactions divided by elapsed time.
• Failed transactions – The number of times the server responded with a return code >= 400 plus the sum of all failed socket transactions which includes socket time outs.
• Longest transaction - The greatest amount of time that any single transaction took, out of all transactions.
A sample of the report ForLinux will produce can be downloaded here. Please note, this report has been produced as a guide only and the information contained within the report is fictitious.
A list of Frequently Asked Questions has been put together to answer some of the most common queries, however if you require further information or have a question which is not covered here, please contact our Sales Team on 0845 4210 444 alternatively please email sales@forlinux.co.uk
