Getting Started with LoadView

5 Steps to get started with LoadView

LoadView is completely web-based and highly intuitive. Forget the pain of spending days for complex installations. Just register for the free trial version or open your unlimited account and start with the real load testing stuff. We reduced the complexity of load test setup, implementation, execution, and analysis dramatically. Whether you are an experienced performance engineer or new to the load testing topic, it won’t take you more than 5 minutes from script creation to the start of your test. LoadView guides you in the five steps outlined below through the whole load testing process.

Step 1: Create your load simulation script or device

Keep in mind that there is no need to implement a high number of load testing scripts for your application. Often 20 percent of the use cases generate 80 percent of the total transaction load. Once you’ve selected the relevant user interactions, you should choose the appropriate user simulation approach. LoadView gives you full flexibility and provides protocol, service and real browser-based user simulation. After all, the objective of your load test and the technology used by your application will help you to find the appropriate simulation type.

Use protocol level scripts for stress tests to simulate a high load on the backend. Load or stress tests of web services use a protocol level simulation approach typically. Due to its low overhead, a high number of scripts can run in parallel on one load injector, which leads to less money being charged.

Real browser based tests should be used to validate end-to-end response times. LoadView comes up with a capture and replays based real browser-based scripting tool called Everystep. Our customers love it because it lets you navigate through your test case and records your clicks. Once done you can add timers to measure custom actions, add verification steps and replay the recorded script. Everystep is part of our load testing a monitoring offering, and you can reuse it also for automated execution of other repetitive tasks in your environment.

Step 2: Validation

Overloaded load injection machines impact end-to-end response times negatively. Therefore, LoadView provides a validation step, which executes a single user test of your test script and calculates the maximum number of user per load injection machine. Calibration prevents you from inconsistent test results due to bottlenecks on a load agent machine.

Step 3: Execution Plan

Marketing campaigns, sales, and other measures can have a huge impact on the number of hits arriving at your websites. Typically, the user requests land slowly in the morning and reach several highs over a full business day. It’s crucial to the success of your load test that you model a realistic execution plan. LoadView comes up with a feature, which allows you to model a real-world load curve. You can specify how fast the user should be ramped up, how long a particular number of user should simulate the load and also how fast they should be ramped down. The execution plan feature of LoadView gives you full flexibility to model a realistic load test scenario.

Step 4: Zone Configuration & Virtual user distribution

We all know that network latency has an impact on web page load times. Considering a web page, which executes 50 sequential server requests during refresh and the developer already, has shown that those backend requests take 10 ms each. The Load time in your data center will be 5 seconds. On locations, abroad such as Asia with a latency of 200 ms, the response times of this website will be 5 seconds for the backend plus 200 ms x 50 requests equals 10 seconds for the network.

Don’t make a mistake and measure response times only inside your data center. LoadView gives you a broad range of load injection machines around the world. Select those who represent the usual location of your customers.

Step 5: Run your test and get your results

Finally, start your configured stress test scenario. The best thing is that you only pay what you get. Prior the confirmation of a stress test, LoadView shows you how much will be charged for this test. You will need to confirm your email address, and LoadView will put your test in the execution queue.

During the load simulation, LoadView displays response time and throughput monitoring metrics in an online dashboard. Once the stress test has finished, you will receive a summary report with a link to the results of this test.

When scalability limits exceeded during a stress test, the error rate is often high. Tuning and operational teams are interested in the cause of this issue. There is no need to repeat such tests because LoadView captures the full breakdown of your website response times. You can use the waterfall chart to get insight in the slow component or watch the video for visual checks how your website behaves under expected load situations.

Finally, you executed the test run and received a detailed test report. The report is very intuitive, and you can fully browse through all results by using your browser. LoadView let you share test results by just sending out a unique link to your team. We removed the test reporting overhead completely.

LoadView keeps older test results for later comparison with new performance metrics allowing you to benchmark the changed application.

LoadView Cheat Sheet

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s