← Back to issue list

CPU max and override for multipass

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1792581
Type
issue
State
closed
Author
~sergiusens
Labels
18.10-build-vm
Created
Updated
Closed

Current evaluation

Resolved by snapcore/snapcraft#2273, commit cbd1854d9, which selected the best available CPU configuration for Multipass.

Resolution: closed resolved

Reason: The maintainer linked snapcore/snapcraft#2273. Its merged commit, cbd1854d9 ("build providers: use the best CPU configuration"), implemented the requested CPU optimization and override support.

Evaluated by: mr-cal-bot

No scores available.

Issue body

CPU needs to be maxed for best performance and have a toggle to allow overriding

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Resolved by snapcore/snapcraft#2273, commit cbd1854d9, which selected the best available CPU configuration for Multipass.
stealth/space-bunny-alpha — closed resolved Multipass CPU allocation was fixed by merged PR #2273 (commit cbd1854d9), selecting the best CPU configuration with an environment-variable override.
stealth/space-bunny-alpha — closed stale The CPU maximization/override request was closed with no documented resolution; no linked PR or commit could be identified.
qwen/qwen3.6-35b-a3b — — Closed without implementation or discussion. The request to max CPU allocation and add an override toggle for multipass was abandoned. No resolution or merge details were provided.
qwen/qwen3.6-35b-a3b — — Closed without implementation or discussion. The request to maximize CPU allocation and add an override toggle for multipass was likely abandoned or superseded by updated build configurations.
qwen/qwen3.6-35b-a3b — — Closed without resolution or implementation details. No discussion or follow-up comments were recorded.
qwen/qwen3.6-35b-a3b — — Closed without implementation or discussion. Likely abandoned or superseded, with no resolution details or comments recorded.
qwen3.6-35b-a3b-mtp-q6 — — Abandoned without implementation. The request to max CPU allocation and add an override toggle for multipass was closed after no discussion or activity.

Update history

Date Change
created

Related work

  • Likely Fixed By: snapcore/snapcraft#2273 (confidence 100%)

    Directly linked by the maintainer and associated with resolving commit cbd1854d9.

Related issues

Issue Project State Summary Similarity
#1795666 snapcraft overcommits CPUs in a multipass environment snapcraft (launchpad) closed Resolved by snapcore/snapcraft#2365 (commit c325c62ad), which reduced the conservative default Multipass CPU allocation to address host overcommit.
80%
#212 Incorrectly handling SNAPCRAFT_MAX_PARALLEL_BUILD_COUNT craft-providers open SNAPCRAFT_MAX_PARALLEL_BUILD_COUNT not honored and Multipass instances hardcoded to 2 CPUs. Maintainer triaged; still unfixed in craft-providers (cpus=2 at multipass_provider.py:300), provider-side work split out to #531, snapcraft-side partly fixed in 8.4.4.
73%
#2008003 Multipass build provider does not support resource settings core core22 snaps snapcraft (launchpad) open Multipass builds of core22+ snaps ignore SNAPCRAFT_BUILD_ENVIRONMENT_CPU/MEMORY; provider hardcodes 2 CPUs/2GB RAM. Maintainer confirmed unsupported; fix tracked upstream in craft-providers#531.
73%
#2365 multipass: change default CPU value snapcraft merged Merged PR #2365 as c325c62ad, setting a conservative Multipass CPU default aligned with memory allocation and adding messages when resource values are overridden.
72%
#1792614 use multipass if set in the environment snapcraft (launchpad) closed Closed as fixed: PR snapcore/snapcraft#2275 (commit 04f8896d9) made SNAPCRAFT_BUILD_ENVIRONMENT/multipass take precedence over the base-derived provider choice.
72%