-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Closed
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.platform-webWeb applications specificallyWeb applications specificallyteam-infraOwned by Infrastructure teamOwned by Infrastructure team
Description
Linux Web Engine builds are running in ~50 minutes, which is substantially over the goal of 30 minutes. One reason for this is that the wasm_release build is not goma-enabled. Even so, the ninja command to build the wasm_release build is still passing a -j of 200, which is way beyond the 8 cores that the Linux VMs appear to have. We need to do two things:
- Use
autoninjarather thanninja -j200to buildwasm_release - Run the
Linux Web Enginebuild on a machine with as many cores as possible.
@eyebrowsoffire Do we (or do we plan to in the next O(weeks)) do a wasm_release build on any configurations aside from Linux Web Engine?
Metadata
Metadata
Assignees
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.platform-webWeb applications specificallyWeb applications specificallyteam-infraOwned by Infrastructure teamOwned by Infrastructure team