The fact that he's running it on IIS through FastCGI seemed to me to be a bigger problem than the fact that he's running WP as well. Not because I don't think IIS is a capable web server, but because Wordpress seems to me to be primarily oriented towards Apache + mod_php. Maybe WP is doing something that's really stupid on IIS + FastCGI but on Apache + mod_php it seems to run fine to me. I just clicked through a poorly visited WP blog of mine while monitoring top and CPU never spiked above 9% use on a 3GHz celeron. (this very same blog until a year ago ran on a celeron 400MHz with no problem as well, btw).
That said, he does have a point that WP's insistence on making everything dynamic is rather silly.
I read this Jeff's blog as some is interesting, but I always laugh at how he is so pro-windows.
When I read he was going to do some web stuff I was wondering if he would use a windows server. I admit I don't keep up on what MS offers in the server side but it seems linux + apache is still a better choice.
Unless you're already extremely proficient on [your tools] but would take a lot of time and tweaking to learn the ins and outs of [other supposedly better tools].
> I read this Jeff's blog as some is interesting, but I always laugh at how he is so pro-windows.
On the plus side, he's not pro-Windows in the sense of being an evangelist or anti-something else. He's been working for a consulting business up until now, and there's great money in .Net consultancy, just like there is with Java. It's just a very different world from the LAMP-style web community.
> I admit I don't keep up on what MS offers in the server side but it seems linux + apache is still a better choice.
People publish working websites all the time on Java+whatever and on .Net+Windows, and Microsoft is working to make Windows/IIS a workable platform for PHP. I would personally recommend a LAMP-style stack for someone trying to decide what web technology stack to learn, but for someone who already knows a different stack, it may not be worth the trouble unless you need immense scale.
That's relevant to his complaints about observed CPU usage but irrelevant to the observation that WordPress makes excessive database calls and doesn't cache intelligently.
That said, he does have a point that WP's insistence on making everything dynamic is rather silly.