What are the performance implications of reflection-based DI Containers?

Reflection-based containers inspect constructors at runtime to build dependency graphs, which incurs CPU overhead and memory allocation costs.

While initialization happens mostly at startup, the continuous resolution of Transient objects via reflection can create CPU spikes and GC pressure. High-performance frameworks use pre-compiled expression trees, IL emit (Reflection.Emit), or compile-time Source Generators to bypass runtime reflection entirely.