Archive for June, 2009

The kinds of spikes we haven’t seen before

Friday, June 26th, 2009

Thriller Album Cover

So, the unexpected passing of Michael Jackson has been causing quite a stir. An unintended consequence of this unfortunate story is that the people hit the Internet to confirm the rumors. They hit it hard, causing downtime at numerous web sites. (Arguably, an even less expected side effect of his passing is that when MJ brought down twitter, Iranians were unable to tweet about their ongoing revolt. Oh, Internet, how fragile you are…)

Is MJ’s departure a unique, record setting event? I doubt it. It’s part of a trend, and I think it’s going to become the norm. We all know that Internet usage hasn’t plateaued yet. In fact, once it does, that will be pretty big news. In the meantime, it continues to grow thanks to increasing connectivity, abundance of netbooks and mobile devices, innovation on the web itself and, of course, a growing awareness of the web’s ever-increasing utility.

Think of the DESIGN GOAL for IPv6: let’s make everything uniquely addressable. EVERYTHING. What were those mad men thinking? What could we possibly want to address? They were preparing for a technology-drenched future. Let’s pave the way for innovation, let’s address devices that don’t even exist yet. That will lead to an incredible increase in connectivity and overall network utility! More, cheaper devices, with new, unforeseen functionality! Everyone benefits.

But that’s just concept. In the meantime, mashup-based cross-pollination of web content is rapidly growing, and the trend is all up from here. That’s not just “people on the web” anymore, that’s people USING the web. This affects everyone. Can the pipes handle it? What’s the horse power behind your web app? If you don’t know, find out, because today’s traffic nightmare is going to be tomorrow’s drop in the bucket.

[Post to Twitter] Tweet This Post 

Average Web Page Size has Tripled Since 2003

Tuesday, June 23rd, 2009

elephants1

Within the previous five years, the size of the average web page has more than tripled, and the number of external objects has nearly doubled. The average page size is currently a little over 300k, according to WebsiteOptimization.com.

There are a number of optimizations that help with larger page sizes.

To take one, example, server-side compression mechanisms provide a good option to negate some of the problems that accompany larger page size, like higher bandwidth costs, and slower page load times.

If your web server is running Apache, mod_deflate can help. If you’re using IIS, there is a good article about compression settings in IIS here.

As with most optimizations, there is a trade-off. In the case of compression, the trade-off comes in higher CPU utilization. A nice overview of compression can be found here. Even though compression raises CPU usage, optimization is a game of trading what you have to spare to get more of what you need, so if you can spare some CPU cycles, compression is a very smart trade.

[Post to Twitter] Tweet This Post 

Half a Second Additional Load Time Costs 20% in Lost Traffic and Revenue

Tuesday, June 23rd, 2009

Stopwatch

I recently stumbled across a blog post with this tidbit from a previous Web 2.0 conference. Google ran a user test to experiment with returning more than the usual ten results at a time in their search engine.

Google found that the half second needed to return the additional results killed user satisfaction, and caused a 20% drop in traffic. In spite of working in the load testing industry where page load time is king, seeing the real consequences of slow page load times drives home the point of “why page load times are important” in a very tangible way.

See Greg Linden’s blog post on this topic.

[Post to Twitter] Tweet This Post 

Google Page Speed Plugin

Saturday, June 13th, 2009

Google recently announced a new open source Firefox plugin named Page Speed. Page Speed is an addition to the already amazingly handy Firebug plugin. It provides an additional tab within Firebug that displays information on how to speed up your web page load time.

Google Page Speed Plugin Screenshot

Google Page Speed Plugin Screenshot

Implementing the optimizations suggested by the Page Speed plugin can help lower your base-line response time. Check it out if you haven’t already!

[Post to Twitter] Tweet This Post 

Common gotcha when load testing apps with ajax polling

Friday, June 12th, 2009

If you’re load testing an app with Ajax that uses polling, or comet, using an http level test (no browser), don’t assume you can safely re-use your script in subsequent load tests. If a developer changes the polling interval, your script will no longer be accurate and the load it generates may be substantially less or more intense than real world traffic. A change like this is easy to miss. Also, if you don’t have content-checks on your Ajax actions, other changes may invalidate your script without you ever realizing it.

[Post to Twitter] Tweet This Post