[perf] resolve: Introduce separate (Local,Extern)ModuleData structures for local and external modules respectively#156407
[perf] resolve: Introduce separate (Local,Extern)ModuleData structures for local and external modules respectively#156407petrochenkov wants to merge 1 commit into
(Local,Extern)ModuleData structures for local and external modules respectively#156407Conversation
… local and external modules respectively
|
r? @wesleywiser rustbot has assigned @wesleywiser. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
[perf] resolve: Introduce separate `(Local,Extern)ModuleData` structures for local and external modules respectively
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (b521230): comparison URL. Overall result: ❌ regressions - please read:Benchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf. Next, please: If you can, justify the regressions found in this try perf run in writing along with @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary -0.0%, secondary -1.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.6%, secondary -2.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 499.454s -> 498.007s (-0.29%) |
The first commit from #156362 for benchmarking.