it's great that they share their findings and part of their code, even if I'm not a .NET dev I find the blog posts really interesting and their approach/tools inspirational.
But wasn't slashdot the first high volume site sharing their solutions to performance issues?
Notice I said .NET. You can find plenty of presentations / blogs on php performance, ruby / rails performance, python / django performance but not many on .NET - I guess simply because most high-volume sites don't use .NET
I'd say it's rather because most high volume sites using .NET are more commercialized , and often run by companies that's typically not been very open about anything they do internally.
Also StackOverflow are one of the few .Net sites hackers/devs flock to and care about. I work on a large scale .Net web app, but I don't think many hacker news readers would really care about the application itself (and, as you pointed out, my company would probably kill me if I started blogging about the internals!).
Yes, I think I remember what you were talking about.
Seemed like /. was one of the first millions-of-hits-per-day site that was heavily dynamic content. All with Perl and MySql, right? I still don't really understand how they do it, but I remember feeling grateful that they were describing it openly.
I always assumed Slashdot was pre-generating static files (every few seconds or so, at least of the main top stories) that were served to the users. Isn't that why their comment form said that your comment might not appear until a few seconds after submitting it?
But wasn't slashdot the first high volume site sharing their solutions to performance issues?