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.

It’s almost that time of year again. Holiday shoppers looking to stay at arm’s length from the seasonal mall madness will undoubtedly turn to the Internet to make their gift purchases. In fact, ShopperTrak predicts national retail sales will rise 3% during November and December this year as compared to the same time period last year.

In order to keep up with this expected spike in website traffic, there are a few steps ecommerce companies should take to ready their site. In order to help, we’ve rounded up the top eight load testing and website monitoring tips to help ecommerce sites stay on their “A-game” this holiday season.

Looking for a way to keep up on website performance best practices, load testing tips and all things related to the success of your websites and applications? Then join us for our new BrowserMob office hours.

We’re pleased to announce that starting October 7, SMEs from our Engineering, Professional Services, Customer Service and Sales teams are at your service for one hour on the first Friday of every month. Feel free to pick their brains and ask anything that’s on your mind. They’re happy to share success stories and lessons learned from their work with other customers.

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.

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.

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.

Recently someone asked if our load testing performance is ever affected by other EC2 users, given the varying levels of EC2 utilization among tests/iterations. The short answer is no. The longer answer is we’ve done rigorous system testing, going beyond Amazon’s extensive measures to provide consistent performance across their cloud network.

While most other load testing tools use 500 or more virtual users per CPU core, BrowserMob is extremely conservative with our capacity (RAM, CPU, disk space, etc.). We use only one browser per core and no more than 50 virtual users. The result: highly consistent measurements and absolute confidence that any poor response times come from the site under test (SUT) and not the testing tool itself.

The Eventually Consistent developer blog reports that after researching on-demand load testing tools, EC loves BrowserMob best. Why? (1) The ability to upload Selenium and run real browsers against your site, (2) real-time reports showing response times/server errors and (3) the downloadable database which lets you run your own queries and analyze them in numerous ways. EC said BrowserMob was “the best way for us, a small shop, to learn about how our site performs.”  Thanks EC and glad we could help.  Read the full post.

© 2012 The BrowserMob Blog Suffusion theme by Sayontan Sinha