Benchmark Early and Often

October 3rd, 2008 @ 9:56 pm
Woah! Hold On A Sec! This post has outlived its shelf life. While it's still here for archive purposes, you should make sure the facts stated herein are still correct.

This past week I had to deal with a new concept: a client site that failed due to excessive load. Most of the week was spent optimizing the site by doing the critical components: installing APC, ensuring that our caching (Akamai) was satisfactory and properly configured, and making performance improvements.

But one thing that became very important was the benchmark test. Using ApacheBench, we identified the blind spots, weak spots, and bottlenecks in our web server (WordPress…duh) and worked to address them.

Running ApacheBench is so absolutely easy. Everyone should do it. The command is simple:

ab -n 1000 http://www.example.com/

That’s it. This calls ApacheBench to do 1,000 hits to your website. It produces a report, showing you important stats like the number of hits per second processed by the web server. It’s also fun to do things like disable APC and re-enable it, and see the difference – here on BrandonSavage.net there is a 480% improvement with APC turned on.

And the best part about ApacheBench is that it comes standard with Apache. No need to install a separate package. It’s fun, fast, easy, and important. If there are bottlenecks in your website, you need to know it…before the load takes it down.

The original work of Brandon Savage.

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks

No related posts.

Categories: System Architecture, Web Architecture
Comments:

Scaling Up: Reducing Drag, Increasing Lift | BrandonSavage.net wrote at 2/24/2009 9:52 am:

[...] life story: I benchmarked my website with APC turned on and turned off. The turned on version was able to withstand some 230 [...]

BrandonSavage.net uses gravatars. Get yours!
Search:
Copyright © 2008 - 2010. All Rights Reserved.