"Maximizing .NET Performance," by Nick Wienholt
During my flights this week, I decided to read Wienholt's performance book. Overall, I thought it was written well and it had a lot of good information. It pretty much hits the sweet spot in most cases, and I learned a couple of things to keep in mind for future .NET development projects. Wienhold covers remoting, exceptions, I/O...pretty much what you'd expect a performance book would address. He also covers using tools to address poorly performing applications, and he also has an appendix that talks about the tool he wrote that gathered the metrics he uses throughout the book (which looks very interesting).
While I felt there were no weak spots within the book, there are a couple of aspects that I think would improve it . First, having a general list of "tips" (for lack of a better word) would really help the developer. I realize Weinhold may be a little skittish giving a list of tips where there may be more issues that have to be addressed than just "do something this way." Some performance tweaks are not always applicable in all cases, so that may be why he didn't include it, but I still think having that list somewhere in the book would be beneficial (either as a list at the back of the book or highlighted points within each chapter). Also, I thought Chapter 15 ("Solving Performance Problems") was a little thin. I think that chapter would be awesome if Weinhold would have demonstrated how you can find hard-to-diagnose problems in code via the tools he mentions .
I think what he has already produced is definitely a good book for any .NET developer to have on their shelves, and I'd definitely recommend it to any .NET developer who cares about making their application perform better.
 I've been leery of posting what may appear as negative comments about another author's book. To make a long story short, years ago I had a "run-in" with another author about comments that I made about his book. Since then, I've withheld making any comments about a book, but I've realized that I'll never find a book the "perfect" book, and so I think it's OK to give constructive criticism (or at least that's what I hope they come across as ;) ).
 It seems like Nick is already thinking about updates, and I like the additions he's planning to add.
* Posted at 06.18.2004 10:33:35 AM CST | Link *