Reflection이 느린 이유

• Why is reflection slow? 글 참고 하여 작성함

배경

• CLR Type System Design Goals
  • Goals
    • Accessing information needed at runtime from executing (non-reflection) code is very fast.
  • Non-Goals
    • All uses of reflection are fast.
• EEClass
  • MethodTable data are split into “hot” and “cold” structures to improve working set and cache utilization. MethodTable itself is meant to only store “hot” data that are needed in program steady state. EEClass stores “cold” data that are typically only needed by type loading, JITing or reflection. Each MethodTable points to one EEClass.

어떤 동작때문에 느린것인가?

• Fetching the Method information
• Argument Validation and Error Handling
• Security Checks

Reflection에는 어느정도의 비용이 들어 가는가?

Reading a Property (‘Get’)

Writing a Property (‘Set’)