Archives

Archives / 2006 / July

  • WCAT: Easy, Magical, Stress Testing for IIS Web Applications

    4 Comments

    Later on, I will show you a pretty cool way to make that UBR file much easier for  you non-JavaScript fans.  But, this should give you the "out of the box" experience for WCAT.

    WCAT Client

    As we mentioned, clients are nothing more than just a "dummy" doing what the "master" (wcctl.exe) tells it what to do.  Thus, all the requests that this client will make are completely dependent on the UBR settings.

    Wcclient isn't fancy, just a .exe that you must call to start a client.  Based on your UBR configuration, the client will "simulate" a number of clients like setting the Client Threads to 80 equals 80 virtual clients.

    The beauty of WCAT is that it can simulate a large number of clients and create very quick web traffic against your web server.  The downside is it doesn't have any built-in logic to determine what constitutues a "complete" request such as requests for images, htm, css's, and many other files that make up a typical web request.  See HTTP RFC for more details...

    Using Log Parser to Generate a UBR File

    Knowing what we know above, we first think "sheesh, if it can't re-create load already hitting my application then it is useless."  I would agree if it wasn't for a very cool tool called Log Parser (all you roadshow attendees you should be very familiar with this awesome tool!) that allows Log Parser to read your IIS Log Files and re-create that traffic against your server.  Did we just say that you can easily "re-create" your traffic?  You betcha... and free!

    Log Parser:  Get The Coolness Here

    To understand how to do this, I suggest that you review the following:

    Read more...