Likely the async reprojection issue. The workaround here https://github.com/ValveSoftware/SteamVR-for-Linux/issues/227#issuecomment-520459572 fixes the major lag for me. Though other reprojection issues affecting performance still remain #395. #469 could also be affecting performance.
Unfortunately there doesn't seem to be any movement from Valve on these in over a year.
Disabling async reprojection globally through the .vrsettings file yielded no result for me. Also the issue #395 is exactly what I experience, but it's not only effecting the vr overlay, it's effecting the entire display/rendered frame.
Update on this issue:
The high frame time is resolved by using corectrl and setting my GPU to it's VR power profile, an upping its GPU and memory speeds to their "normal" compared to speeds on windows.
Hope this resolves other's issues of poor performance while on an AMD system.
Nothing extracted yet.
Describe the bug
When trying out VR once again on linux using the Valve Index, I've noticed that this issue is still going on; whether I use Steam(Runtime), Steam(Native), SteamVR(beta), SteamVR(stable), SteamVR(Older build for linux users), my HMD's response time is way to high, making the view in the hmd lag behind where my actual gaze should be, creating this dizzying effect in the headset that strains the eyes. I've also noticed that frame times are way higher than what I had on windows, especially when not in steamvr home or any vr apps (on windows = >1 or 1ms at 90hz, on arch linux <3ms at 90hz).
To Reproduce
Steps to reproduce the behavior:
Expected behavior
From the experience I had on Windows 10 and 11, I expected my view to have a 1 to >1 ms response time.
System Information (please complete the following information):
nvidia-settingsorvulkaninfo | grep driverInfo: Mesa 22.1.7Performance Data (optional, but very helpful):
Could not perform the last two instructions due to SteamVR(beta), SteamVR(Stable), and SteamVR(Linux_v1.14) not providing the options described in the instruction set.
Screenshots

Additional context
n/a
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" and "Perf Data" sections in their replies.