How often should we be measuring?

Testing performance is tough.  As a product is being developed, you need to track the performance of what you’re building.  The question is how often? It turns out it’s a very difficult and time consuming thing to identify the cause of failures in a performance suite when the amount of change to the product is large. …

0

The best laid plans…

I started this, as most do, with the best of intentions.  A long list of topics to discuss, potentially interesting things to say, and so forth.  Then, as is usual, life interrupted. So, I put forth the question to the proverbial teeming masses of the readership:  What do you want to know about testing performance? …

2

Timing your code

Timing your code One of the fundamental aspects of performance testing is identifying how long it will take you to execute the code you’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…

2

What To Watch

[Housekeeping stuff.  I added categories.  Neat stuff.] RichB asked me yesterday in the comments to my first post: “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?“ This, unfortunately, is not the…

1

Managed Code Performance

I never quite know how to start something like this without sounding a bit goofy.  “Hi there” 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…

4