socketdev Optimizing Compiler Performance
Use only after profiling identifies generated-code cost. Record the release artifact, compiler/runtime version, target, workload, baseline, and before/after result.
- Read the shared compiler/codegen audit.
- Prefer representative PGO evidence over manually guessed branch or inlining hints.
- Scope LTO, target features, cold annotations, and CPU dispatch to supported targets.
- Compare code size, build time, startup, peak memory, and tail latency as well as the selected hot metric.
- Keep the change only when correctness tests and the same representative benchmark pass.
For parser layout, use optimizing-parser-performance.