Swift Compiler vs in Pipeline Benchmark

Measured with: swiftc -typecheck on a single file when there is no local Package.swift; when there is a package, scripts/swiftc-bench-typecheck.sh (same Sources + Generated inputs and Clang flags idea as in-cli sil_emit) after a timed swift build. Also package-context swift build (SwiftPM reference) and in build default (native hybrid pipeline only, no SwiftPM). in column = inauguration compile path (scheduler + SIL passes today); swift build = legacy SwiftPM baseline until native codegen fully replaces it. hybrid-cli matches the native wave harness without the in CLI wrapper overhead. Wall times: median over 3 timed runs; min–max across those runs shown in parentheses next to medians (easy tables) or inline (detail table).

Benchmark Environment

Easy Copy/Paste

ExampleSwiftPM swift build median (min–max ms)in native median (min–max ms)
aurorality/examples/counter984.37 (952.47–1004.23)548.29 (540.68–578.89)
aurorality/examples/basic943.56 (936.91–1000.56)559.43 (541.97–608.84)
aurorality/examples/hyperchat433.33 (386.77–614.14)4334.97 (3155.60–4571.39)

SwiftPM Package (Preview Host) Benchmark

ExampleSwiftPM swift build median (min–max ms)in native median (min–max ms)
runtime/swift-preview-host681.30 (647.08–781.19)771.99 (725.52–774.55)
Exampleswiftc med (min–max)SwiftPM med (min–max)in native med (min–max)hybrid-cli med (min–max)native÷SwiftPMin-stage-total(ms)in-driver-overhead(ms)in-wrapper-overhead(ms)loss bucketswift build okin ok
aurorality/examples/counter395.13 (395.11–414.95)984.37 (952.47–1004.23)548.29 (540.68–578.89)7.05 (6.87–7.17)0.557538.8479.447541.248win
aurorality/examples/basic402.42 (371.62–412.28)943.56 (936.91–1000.56)559.43 (541.97–608.84)6.84 (6.06–7.15)0.593550.6368.792552.593win
aurorality/examples/hyperchat2326.91 (1966.04–3817.95)433.33 (386.77–614.14)4334.97 (3155.60–4571.39)15.00 (8.19–15.83)10.0044319.77615.1944319.970swift-frontend-stage