Idea: # Significant Performance Difference Between Longshot and NX2navi #1912
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1912
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?
The idea
Significant Performance Difference Between Longshot and NX2navi
Longshot is delivering approximately 50% lower performance than NX2navi in the same Nintendo Switch 2 game, and Longshot also exhibits noticeable stuttering that is not present in NX2navi.
This is not a minor difference. Both projects are implementing Switch 2 emulation through Vulkan, and both have substantial replay optimizations. NX2navi demonstrates that this workload can run significantly faster and with smoother frame pacing.
What I am experiencing
Why I believe this deserves investigation
Looking through the two projects' Vulkan implementations, I found that both already implement several similar optimizations:
Longshot already has parallel replay and submission batching, so simply adding those features is not the answer. The important question is why its implementation is performing so much worse.
Some areas of the Longshot implementation that deserve profiling include:
What I am requesting
Please investigate the performance difference between Longshot and NX2navi, identify the bottleneck, and implement the necessary optimization or fix.
I am not asking for a collection of configuration tweaks to work around the problem. I am reporting a substantial performance difference between two implementations targeting the same hardware and workload.
A roughly 50% performance gap, combined with stuttering that does not occur in NX2navi, suggests there is meaningful optimization work to be done in Longshot's Vulkan execution or synchronization path.
Anything else
No response
Possibly related, for context: