nodejs / nodejs/node

Backport Windows PGO + ThinLTO from main to v24 LTO builds for builds (x64 and Arm64)

Open
#65,452 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
JavaScript
Stars
122k
Forks
37.3k
Avg merge
4d 2h
Merged PRs (30d)
283

Description

What is the problem this feature will solve?

Improve performance of Windows builds by 15% by backporting the perf improvements brought through PGO and ThinLTO enablement, from v26 to v24 LTS releases.

See issue #61964 for work description for the v26 changes.
Separate perf suite results are here
ThinLTO: https://github.com/JaneaSystems/node-thin-lto-perf
PGO: https://github.com/JaneaSystems/node-pgo-perf

What is the feature you are proposing to solve the problem?

Backport the relevant PRs (and related config changes the the build):

  • [nodejs/node] Enable PGO for Windows builds (x64 and Arm64) (I #61964)
  • [nodejs/node] build,win: enable PGO and LTO for Windows builds (PR #62761)
  • [nodejs/node] build,win: build,win: replace LTCG with Thin LTO for releases (PR #63114)
  • [nodejs/node] build,win: fix VS2022 arm64 PGO build (PR #63413)
  • [nodejs/node] build,win: add PGO workload scripts (PR #63696)
What alternatives have you considered?

none

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with issue #61964 and the listed PRs #62761, #63114, #63413, and #63696 to understand the Windows PGO and ThinLTO changes. The work is done when the relevant configuration is backported to v24 and Windows LTO builds succeed for both x64 and Arm64.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.