Idea: Reserve CPU threads during builds for everyday use #148
Labels
No labels
area/build
area/install
area/saves
area/tooling
area/ui
area/updates
ci: approved
good first issue
gpu/amd
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
platform/linux
platform/steam-deck
platform/windows
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher#148
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reported on Discord
What would you like?
Add an option to reserve some CPU threads so the PC remains more usable for regular tasks while Longshot is building. Optionally let users opt into using all available CPU resources for maximum build speed.
Why?
Builds can use enough resources to make the computer difficult to use; reserving threads would trade some build speed for responsiveness, while an opt-in maximum-speed mode preserves the fastest option.
Context
The request followed a screenshot showing the launcher building Longshot v3.0.0-rc.5 at 1%, with an estimate of about 1 h 36 min remaining. The reporter said their PC took five minutes to take a screenshot. No system specifications or build log were provided.