Reflection : Dodge Common Performance Pitfalls to Craft Speedy Applications

Joel Pobar has produced an excellent article on the costs of reflection that offers good insight into best practices.

Comments (1)

  1. Stu Smith says:

    Why does new T() in a generic function use Activator.CreateInstance, if it’s one of the slowest reflection calls? I know the idea is to share code where possible, but in those specific cases where a new object is created, wouldn’t it be better to emit separate cases for each type?

Skip to main content