Bill Wert's weblogStriving to make managed code fast...Timing your code- March 11, 2004 Timing your code One of the fundamental aspects of performance testing is identifying how long it will take you to execute the code you&8217;re writing. There are a few ways you can measure this: measuring time elapsed while your code executes, computing how many instructions it may take and extrapolating time from there (based on target hardware), or I suppose you could guess. I can&8217;t recommend the last option, however. Hopefully, you&8217;re reading Rico. He has a.http://blogs.msdn.com/billwert/archive/2004/03/11/88192.aspx What To Watch- March 9, 2004 Housekeeping stuff. I added categories. Neat stuff. RichB asked me yesterday in the comments to my first post: &8220;What are the range of metric values I should expect to see for a given scenario. For example, how many gen1 collections per minute is OK for a heavily loaded web app&8220; This, unfortunately, is not the kind of advice I can give you. Rico or Jan are far more likely to have useful answers to that kind of question - they're design kind of guys. Being a.http://blogs.msdn.com/billwert/archive/2004/03/09/86858.aspx Managed Code Performance- March 8, 2004 I never quite know how to start something like this without sounding a bit goofy. &8220;Hi there&8221; seems odd, seeings as I have no real idea who I'm talking to yet. Ah well. My name is Bill Wert. I'm a Software Test Engineer on the CLR Performance team. I started this blog in hopes that I can fill what I see as a niche. People like Rico talk about what kind of design patterns can lead to bad performance. The message at the end of the day is that...http://blogs.msdn.com/billwert/archive/2004/03/08/86292.aspx |