During MIR inlining, we end up producing larger MIR bodies each, as inlining often causes an increase in MIR for non-trivial functions being inlined. This perf run shows that in the incremental cases, we lose some time to optimized_mir as expected but this is often offset by wins in codegen.
However the other place we regress is time spent dealing with the incremental cache. That suggests to me that our MIR is larger due to inlining which causes more time to be spent during serialization/deserialization.
It might be worth exploring if there's any optimizations we can make to the serialized Body representation.
Originally posted by @wesleywiser in #68828 (comment)
During MIR inlining, we end up producing larger MIR bodies each, as inlining often causes an increase in MIR for non-trivial functions being inlined. This perf run shows that in the incremental cases, we lose some time to
optimized_miras expected but this is often offset by wins incodegen.However the other place we regress is time spent dealing with the incremental cache. That suggests to me that our MIR is larger due to inlining which causes more time to be spent during serialization/deserialization.
It might be worth exploring if there's any optimizations we can make to the serialized
Bodyrepresentation.Originally posted by @wesleywiser in #68828 (comment)