Congratulations: you’ve run a few LoadImpact load tests and you’re anxiously poring over the results. You’ve probably already gained a few insights about what you might improve. You’ve seen some areas you want to explore further. And you’ve found some mysterious status codes in the URLs tab on the test results page.
For an e-commerce site, performance is key, especially during peak traffic periods. We often talk about preparing for Black Friday and Cyber Monday as traffic peaks. But realistically, those days aren’t the only days where traffic peaks.
[Editor's Note: We've updated this blog post on Dec 4, 2018 to include the k6 open source load testing tool. k6 was not originally included in this tool review as it was launched after the blog was first posted.]
There are tons of load testing tools, both open- and closed-source. Open-source tools are growing in popularity, and we use mainly open-source software (OSS) at Load Impact, so we thought it might be useful to take a deep look at the available options in a detailed open source load testing tool review. (We'll call this our version 1.1 review.)
tl;dr — This post is about using Google Analytics to determine how many concurrent users to specify in your load tests.
- "Hourly Sessions x Average Session Duration (in seconds) / 3,600" is the formula we recommend to get started
Your application has been localized, your website is responsive, you've even built a mobile app - how about your performance?!
T'was the season to deliver a seamless online user experience, to bring under two second response times to shoppers looking for the best pre and post Christmas sale. Except that it wasn't. At least not for the following five companies.
We're offering to provide the technology taskforce responsible for fixing the troubled HealthCare.gov website free use of our performance testing services until the Obamacare website is functioning at full capacity.
Just recently we launched our cloud-based Server Metrics Agent - a function that allows you to collect information about what's happening internally on your servers while your website or -application is being load tested. Installing the Server Metrics agent on one of your machines will immediately let you see how much CPU, memory and network bandwidth the server is using throughout the load test.
In a recent post, we talked about the difference between load testing tools and site monitoring tools. Another quite common question is what the difference is between Load testing tools and page speed tools. They both measure response time and they both are important when it comes to assess the performance of your web site. So what it the difference and which one do I need?