Tech-Ed 2007

Tech-Ed 2007 is starting tomorrow and the Profiler Team is sending a few people to sunny Orlando for the event. This is great news for me because my boss, Steve Carroll, is away for the week (just kidding Steve), but it is really great news for folks at Tech Ed because he’ll be there presenting…

1

Learning to Profile

I went to a meeting with Rico the other day and he showed us a few approaches he uses when solving performance issues. He is a performance engineer with many years of experience so it really was a case of watch and learn. This got me thinking about how people can best learn to use…


C# for C++ Devs: Structs vs Classes

I’m from a C++ background and now I’m working quite a bit more with C# so I’m learning new things all the time. One thing that baffled me recently was caused by the difference between structs and classes in C#. In C++ the only difference between struct and class is the default member accessibility. For…


Basic Profiler Scenarios

This post was going to cover some basic scenarios discussing the differences between sampling and instrumentation and when you would choose to switch methods, but then I found there is already something like that in MSDN. If you haven’t already, go and take a look. See if you can improve the performance of the PeopleTrax…

1

Why Performance Matters

Everybody likes to think that what they’re working on is important so this is why I think performance (and measuring performance) matters and why it matters now more than ever. In the past chip manufacturers like Intel and AMD did a lot of the performance work for us software guys by consistently delivering faster chips that often made performance…

2

There’s a Profiler in Visual Studio?

I’ve just started working in the Visual Studio Team System, Profiler team. Many people are surprised to hear that Visual Studio does actually have a profiler and that it has had one since Visual Studio 2005. To use the profiler you need either Visual Studio Team System for Developers or Visual Studio Team Suite. So where…

3