Signin
Stressing ASP.NET

I ran Microsoft Web Application Stress Tool on this blog which uses a variation of dasBlog, an ASP.NET wepapp, running on 2GHz P4 with 1G of memory and the initial result isn't too bad even though ASP.NET caching is off.  Throughput was about 90 pageviews per minute (17 hits/s at 200K/s) over an hour with only a handful of connection failures.  It's not mindblowing performance, but it doesn't stink either considering my server is a low-end box that cost about $800 to put together.

Going through my logs using Urchin, I see that about 7000 pageviews per day were served on the average for the first 12 days of January.  So this blog is using about 5% of the server's capacity.  January is a slow month so I think 7%-10% seems like more reasonable.  Hmm.

Comments
You're right about it being pointless to tune further once acceptable performance is reached. 1.5 dynamically generated hits/second (I am assuming most of the 17 hits/second are static content such as images or CSS) is abysmal performance on a machine such as yours, however, by at least an order of magnitude, even when using slow languages such as Tcl or Python. There might be a configuration error such as using too few database connections.

You have to keep in mind any geek website could be slashdotted. In that event, even a 20x safety margin is likely not to be enough. That's why I generate static HTML pages, Radio-style, for my own blog from a Python-based tool rather than serve them dynamically. Sure, I lose the ability to host comments, but as those are abused by spammers anyway, not a big loss compared to the added robustness.

Comment has been disabled for this post.