Benchmarking mistakes, part four

Part four of my beginner-level series on how to write bad benchmarking code can be found here.

I'm back from my summer vacation and getting caught up on a mountain of accumulated email. As I mentioned last time, I'm taking the rest of August off of blogging; see you in September!

One thought on “Benchmarking mistakes, part four

  1. I might be missing something obvious here but... You said:

    Usually the number of objects that survive to the next generation because they need finalization is extremely small, so this situation usually does not produce a measurable impact.

    Then why do you even need to wait for those objects with: WaitForPendingFinalizers?

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>