Idea: Reduce CPU use during automatic game updates and copies #163
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#163
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?
Investigate and, if possible, reduce CPU utilization when the launcher updates or copies game files using the Automatic method. The reporter says this can reach 100% CPU and make the computer practically unusable until the operation finishes.
Why?
The high CPU usage significantly affects system responsiveness during updates or copies.
Context
Launcher version: 1.0.0-rc.10
System: AMD Ryzen 7 5700X3D
The reporter observed the issue while updating or copying game files with the update/copy method set to Automatic. No operating system, launcher log, or additional reproduction details were provided.
Related: LongshotLauncher#148 tracks an idea to reserve CPU threads during builds, but this report concerns updating or copying game files with the Automatic method.
From Discord:
The reporter clarifies that the 99% CPU spike occurs when shader preparation begins, not during the earlier file-writing stage. Screenshots show Launcher v1.0.0-rc.10 updating to Longshot Nightly 403 · 544229a2: Task Manager shows 36% CPU while “Gravando a pasta do jogo” (writing the game folder), then 98% while “Preparar shaders” is at 3% (0:29 / ~8 min). System shown: AMD Ryzen 7 5700X3D, Windows. This points to game shader preparation rather than launcher file copying; existing game shader reports are on other systems/conditions.