As you’ve likely seen, we pulled together a comprehensive list of load testing best practices for you to visit, and revisit, at your convenience to help you maintain high performance websites and applications that keep your customers happy.

As helpful as we hope these guidelines are, we know sometimes our readers want to hear how load testing works from the end users themselves. We’ve compiled a few best practices that have come right out of the mouths of customers using our load testing services:

Test different types of traffic at different times of the day.

A LinkedIn user recently posed the question: “What are the best practices for monitoring, collecting and analyzing traffic data for a large content site?” Ian White, lead engineer at Neustar, jumped into to tell readers why active monitoring is just as important as analytics. Website monitoring ensures your site is functioning properly anytime from anywhere.

Below we’ve outlined a few of his key points that will help you monitor your site so you can sleep well at night knowing your website is always up and running.

Stay in the driver’s seat and in control!  When launching a new website or application there are many things to consider to get ready to go “live” – and one of the most important aspects is load testing.

Simply put, load testing helps you determine how many customers the website or application will support – before you potentially find out the hard way (i.e. when users actually come to your site and you have to scramble to make last minute capacity improvements).

Following our blog series on Load Testing Best Practices, Webmetrics will be hosting a Twitter Chat for you to ask any and all questions about load testing.

We just wrapped up our five-part Load Testing Best Practices series. We hope you find these steps simple and convenient as you embark on your next load test.

Planning
When planning a load test, make certain you take all variables into account. For instance, before you load test a website or application, you should ask yourself the following: How much load should I test with (stress test vs. load test)? How many tests should I run? Should I test on a real or virtual browser? Once you have answered these, you will be ready to start and configure your test.

Do you know where your website traffic is coming from? How about the percentage of traffic coming from various regions?

A new report from, comScore, a market research firm, found that nearly 24.1% of total number of users visiting Amazon’s retail website in the month of June, came from the Asia Pacific region. Similarly, 24.9% of the total traffic on Apple’s website are from this same region.

As companies continue to expand their brands globally, it becomes increasingly important to keep track of where traffic is coming from, as load times and performance may vary depending on the region.

Introduction

Welcome to the 5th and final blog in our Load Testing Best Practices series. Today we’ll be focusing on how to make sense of your load test once it’s complete and then dig into the data to help locate the cause of any problems you’ve uncovered.

What do we mean by Analysis?

The goal of running a load test is to identify if your website has any performance or capacity issues, and if so to use the test results to zero in on the possible causes. You want to point your developers and system administrators in the right direction to fix the problem.

Welcome to Part 4 of the Load Testing Blog Series. I’ll be focusing on the type of metrics that are captured while a load test is running as well as some best practices to prepare for when running a test. In my experience, the most useful metrics while a load test is running are:

• Number of successful transactions
• Number of page views
• Page load times
• Number and types of errors
• Throughput

Execution Checklist:

Hello Readers!! Welcome back to Part 3 of our Load Testing Best Practices series, which focuses on writing good load testing scripts.

As I’m sure you would agree to, load testing is an imperative part of every development effort. One of the key components to your load testing efforts is a good load testing script that simulates real user behavior on your web site in the most realistic and accurate way possible.

Before you take a deep dive into the scripting, there are few things you need to plan ahead of time.

So you reviewed part 1 of our best practices blog series, “Planning” and now you are wondering about configuring your test.  What are all the pieces that need to be thought about and configured?  Fortunately these are not complex questions; you just need to know some basic information:

  1. Where do you expect or see web traffic coming from?
  2. How many users come to your site?
  3. How should you apply your user load during the test?
  4. Should you test with virtual users or real browser users?
  5. Where do users spend the most time on your site?

This is the first part of a five-part blog series that will cover all the aspects of load testing, including planning, configuring, scripting, executing and analyzing. This first article focuses on the key areas and questions to consider when planning to run a test.

Why test?

I generally see customers greatly OVER-estimating their expected capacity and many are often shocked when they get the first set of test results back from us. Usually, there is a lot of work to do in order to get the website or application tuned up and ready for a full production release.

© 2012 The BrowserMob Blog Suffusion theme by Sayontan Sinha