Bonjour Foxes!

I started my career as a Telecom Engineer for Rational Software in the load testing space back in the late 90s, and when I look back on the last decade, there were enormous advances in the broader IT world including development methodologies, processing speeds, network speeds, mobile devices (it’s hard to believe the first iPhone was only released 6 years ago). But the question is, has the world of load and performance testing really changed all that much? Are the missions the same? Are the challenges different? And how can we be prepared for the future of load and performance testing?

Let’s start with what hasn’t changed:

  • Websites crash.
    Crashes are a reality today just as much as they were 10 years ago. While many companies have become aware of big events (e.g. Cyber Monday, big ad campaigns) that cause traffic spikes, exact traffic levels are still difficult to predict. One big difference between now and then is the sheer number of websites on the internet. According to Netcraft, the number of active sites on the internet has increased by almost 1000% over the past ten years. More websites = more crashes.
  • Developers still think their code is bug-free.
    Being a load tester can sometimes come with the occasional power trip that results from crashing an application written by developers who think their code is perfect. While I’m sure their code is very good, load testing can still quickly uncover any flaws in the code or architecture that can cause performance issues.
  • Load testing is still pushed off until late in the development cycle.
    This is a reality most testers just have to deal with. Testing in general, but particularly load and performance testing are held off until the end of the development cycle, which can be particularly frustrating for testers who can be blamed for holding up a release.
  • HTTP is still a connectionless protocol.
    Furthermore, it’s being used to drive a world that is becoming increasingly connected. In fact, the vast majority of advances in web technologies (cookies, sessions, AJAX, WebSockets, SPDY, etc.) have been created in order to overcome the HTTP connectionless limitations. For load testers, this means it still causes complications.

What has changed?

  • Load testing is becoming a mandatory step in the development process.
    I’ve been talking to more and more companies these days that are requiring that all applications go through load and performance testing before they’re deployed to production. This is especially true for new online services who know that they only have one chance to show their best or likely lose that customer forever.
  • The performance of applications is becoming more important than the breadth of functionality.
    For some companies like insurance and banks, the importance of application performance is much higher than the pure number of functions their apps can perform. This means that load and performance testers are playing more prominent roles within these development organizations.
  • The number of technologies built over HTTP is growing each month.
    More and more technologies are being developed to make the web faster, more secure and more reactive, and more and more development organizations are adopting them at faster rates. This means load testers are required to test apps containing complex technologies they’ve never seen before, and it’s no easy task to test apps utilizing AJAX, SPDY, WebSockets, video streaming, etc.
  • App developers have to consider the performance of their apps on mobile devices and networks.
    Morgan Stanley has predicted that mobile internet users will surpass desktop internet users by the end of the year. With this in mind, performance testers need to be able to recreate the use cases and network conditions actual users will experience with several different network types and several different devices.

What can you do to handle the realities of today and be prepared for load testing world of tomorrow?

  1. Don’t avoid load and performance testing.

    If you’re one of those people who think your apps will be fine and users will do the testing in production, I hope for your sake that your developers actually do write bug-free code. Remember, your end-users will not be as forgiving or as patient as virtual users are when your application is under high load if you recall the old Amazon.com statistic about losing 1% of sales for every 100 ms delay in response times.

  2. Make your tests as realistic as possible.

    Load testing is much easier these days with the tools available, but don’t think it’s a “point & click” operation. I see too many companies running “load tests” that do not simulate the number of users observed in production nor the conditions under which the apps will be used.

  3. Make sure your load testing tool can match the rhythm of the technical “dance”.

    Developers and architects are going to want to take advantage of the latest technologies, even some that are still in beta. As a tester, you and your tool shouldn’t be the bottleneck for the product launch. Make sure your tool supports your needs as well as the needs of your development organization.

With all of the advances in web and mobile application technologies and the instant response times end-users expect these days, the performance of applications is only going to grow in importance. My advice to load testers is to stay on top of these trends because they move quickly. It’s certainly an exciting time to be a load tester.

, , ,

9 Responses to “Load Testing: Same Old, Same Old or a Whole New Ball Game?”

  1. Jeff Holland says:

    Well stated Herve. Things have indeed changed in the Perf/Load testing space. Something that has also changed in this area is visibility. It’s not at all uncommon to read in the papers or online about a website or online service outage (Bitcoin, RIM). The impact this can have on the company can be immeasurable and very expensive. It’s always been true that company/brand reputation is a key driver of proper perf/load testing but it seems to me that this is even more important now than it was 10 years ago. The instant “negative” visibility that results through apps like Twitter, Linkedin, Facebook, and even the 24 hour news, is something that more and more companies are becoming aware and fearful of. This is helping to drive the push for proper testing beyond what we saw back in the 90′s.

    • Hervé Servy says:

      Hi Jeff, and thank you for your feedback. You are right, “visibility” is a bigger issue today and bad news travel faster than 10 years ago. Sometimes a website crash is justified by marketing people as the necessary evil of a very good campaign… Have you noticed this too?

  2. Alex Podelko says:

    Fully agree with what stays the same – but don’t quite agree with what changes.

    While in some places performance testing became mandatory – I hear more and more stories about companies disbanding performance teams to cut costs. In many web startups (some of which are pretty large) people often don’t want even hear about load testing.

    Many technologies over HTTP – well, it is even simplification, before we had many completely different proprietary technologies.

    Mobile? Well, definitely new – but is it so drastically different from the point of performance testing?

    So I’d say same old – with new details.

    Regards,
    Alex

    • Hervé Servy says:

      Hi Alex. Thank you for your comment. I do agree that mobile is bringing many new challenges. From my point of view, these are technical challenges (capacity to record on the device, capacity to emulate network conditions, etc.). Mobile load testing does not change the load testing discipline by itself. Don’t you think? Mobile testing is still very focussed on the application (functional tests, platform test, etc.), and not enough on the server side… That’s my feeling.

  3. “HTTP is still a connectionless protocol.” Is this a typo?

    HTTP is a stateless protocol. It is most certainly not connectionless. On the contrary, I have a hard time imagining how HTTP can be used without a connection.

  4. [...] 2) Load Testing: Same Old, Some Old? Or a Whole New Ball Game? [...]

  5. Mark Bairden says:

    Hi,

    A good article. My experience has shown the absolute requirement for proper load testing, but it has also shown that the expense is something the project would rather avoid.

    In large companies performance and load testing is often a requirement of release standards. What the project is looking for is a tick in a box, rather than seeing the potential gains load testing can bring to their project. This is why it is so often pushed to the end of the release cycle.

    Cloud computing has also brought its own challenges. I have met the opinion often that performance is not a challenge in the cloud, where resources are imagined infinite. I was told by one developer “Performance is moot in the cloud”.

  6. Alvaro says:

    It makes an adjustment when you stumble upon such a wonderful article really meant for readers as opposed to online search engine, great
    read!

Leave a Reply