To provide a better experience for those of you with large screens, we've now optimized the layout of the Load Impact app to provide a better experience for large screens. Check out the new responsive layout: why now? We'll share that, too.
You and your team have been pushing plenty of updates to your app over the last few weeks in preparation for a marketing milestone.
Everybody in the company is excited, and you can’t wait for users — and potential customers — to see what you’ve cooked up for their enjoyment.
But you haven’t been continuously performance testing throughout development (a bad move, but we forgive you), and you just realized it’s time to start running load tests.
Never fear! We’ve broken down a few steps to get your load testing extravaganza up-and-running, and from there you can smoothly transition to continuous testing, which will save you from this headache in the future.
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.0 review.)
Simulating real traffic patterns is the best way to get actionable results from your load tests. That includes creating tests that closely mirror where your traffic is coming from.
The latest Load Impact update brings the ability to generate load from six additional Amazon Web Services Regions around the world in your load tests.
This webinar not only shows you how to automate load testing in your CI pipeline, but you’ll also learn how Julien applies Microsoft’s best practices to the DevOps and “continuous” mindset while embracing the world of open source software.
Continuous load testing throughout the software development process improves your understanding of your website, application and infrastructure performance.
Developers around the world are discovering that load testing isn’t just a one-off project or something you wait until the last minute to do.
Integrating load testing into your DevOps and Continuous Integration lifecycle helps you achieve a few things.
- Load testing is yet another task you can automate — and we know that’s a good thing
- Understand the performance impact of each code commit
- Plot your app or website’s performance trend over time
We’re constantly collecting feedback from our users in an effort to improve your favorite performance and load testing software.
Here are a few items we’ve recently pushed live into our app for your convenience.
The goal of performance testing is to get actionable data that will help you optimize your website, app or API performance.
The best way to do that is to create the most realistic load tests possible. We like to dish out tips on how to do that in many different ways. To name a few:
- Use the Load Impact User Scenario Recorder to create your load testing scripts
- Look at your traffic data in Google Analytics when figuring out how many concurrent virtual users you want to test when figuring out your performance baseline
- Run multiple types of tests to see how your app reacts under different kinds of pressure
This is the time of year when you’ll often hear people say, “New year, new me.”
While plenty of resolutions will be broken by the end of January, we’ve made a change that we simply can’t go back on now.
We’re very excited to announce that we’ve increased the number of concurrent virtual users our premium subscribers can configure in their load tests — at no extra charge!
The goal for any software developer when performance testing is to get back actionable data from their load tests.
In order to prepare your application and infrastructure for real-world traffic, you need to create user scenarios that mirror real-world behavior.
Instead of asking our users to write custom user scenarios in Lua from scratch, we created the Load Impact User Scenario Recorder. It’s a free extension on the Chrome Web Store.