Repository navigation
Enable PGO for Windows builds (x64 and Arm64) #61964
Description
Activity
- added a commit that references this issue
on Apr 23, 2026 - added a commit that references this issue
on May 20, 2026 - added a commit that references this issue
on May 22, 2026 This issue has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.Reopening this, since it is still in progress.
A short update: Thin LTO is already enabled on Windows and used in releases. PGO workload scripts are approved and should land soon, and I've done tests for enabling PGO in the release CI.
I just never commented on this issue, so it got marked as stale and eventually closed.
- added a commit that references this issue
on Aug 20, 2026 - added 3 commits that reference this issue
on Aug 25, 2026 - added 2 commits that reference this issue
on Sep 7, 2026 This issue can be closed now. LTO has been enabled in Windows releases since v26.3.0, and PGO has been enabled in v26.9.0.
What is the problem this feature will solve?
Profile Guided Optimization has been available for some time now, and stats from projects that adopt PGO commonly show runtime perf improvements of around 10%. LLVM and MSVC offer PGO when building Windows apps for x64 and Arm64 ABI apps.
This request is to investigate and implement PGO in the CI release jobs when building Windows versions of nodeJS for both Arm64 and x64 ABIs.
Overview of LLVM PGO process:
https://llvm.org/devmtg/2020-09/slides/PGO_Instrumentation.pdf
What is the feature you are proposing to solve the problem?
Add to the CI release jobs:
What alternatives have you considered?
nonw