[viewer] Massive performance hitch when running two Slipstream viewers at the same time #403
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Blocks
Reference
sky_line/Slipstream#403
Loading…
Add table
Add a link
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?
Source: in-viewer report (Help > Report Bug)
Reporter (avatar name as given; not verified):
System
Description
Steps to reproduce
not given
Filed by the Slipstream report relay. The reporter's identity is not verified; system details are as sent by the reporter.
Part of #405 (RAM/VRAM management epic).
Possibly the same host-memory exhaustion as #458 (AMD, Windows; a 16 GB machine running two viewers). See the triage there. The fix in progress should help; please re-test on the next beta.
Likely related to #462 (AMD on Windows, high memory while shaders compile). Fixed in 1.1.0 Beta 3; please retest on it.
Tested Beta 1.1.0.3 by logging in a busy sim with two accounts. Massive slow downs persisted. Viewer logs sent through in-game IM.
Tested again on Beta 1.1.0.8, with the Maximum video memory option under Advanced Graphics Preferences set to 3 GB on both viewers, as per instructed given my 8 GB GPU. Was able to go through the same sim used in both tests, but this time without the massive slowdowns previously reported. After going around the sim, I reset the Maximum video memory option back to Auto in both viewers, and sure enough the hitches came back.