Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Strange!
Maybe i read it wrong and it was only a warning, that when i run the game from an hdd, the performance will suffer?
The NVMe interface can be very fast, but specific SSD drives can be slow, either occasionnally or even often. It could be that the flash chips are actually slow, or that the flash controller is performing some garbage collection (usually this follows a recent burst of writes).
You could for instance run this command in a terminal, assuming your drive is /dev/nvme0n1:
> iostat -dtx 1 nvme0n1
Pay attention to values for all the "*_await" columns, those indicate latencies for various requests to the drive. r_await (reads) is usually the most important, as it is the most likely to directly impact an application (the other request types can usually be issued asynchronously).
Update: I had Firefox closed and it's at 0.00. With OBS running I'm still at 0.00. It seems Firefox reads from the NVMe drive which causes a bit of a latency issue... Anyway, thank you for your help.
Update 2: I'm thinking it might be a good idea to have another NVMe drive just for Steam games in order to keep the latency low. I already have one for boot/OS drive and another NVMe drive for my /home partition. Maybe one day I might add one...
I don't know exactly what triggers the warning you got, so I am not sure what you should be looking for: it could be that it's because a performance measurement (in the game code) doesn't meet some expectations (IMHO that's hard to get right), or it could be that the device name as presented to the code via Proton/Wine doesn't look like an SSD.
Does it warn every time? If so, then I'd assume it's caused by some bogus device name. If it's irregular, then I'd assume it's some kind of measurement, and a warning is given above some arbitrary threshold for latency.
Now, if we assume it's the game measuring drive latency...
If your r_await (i.e. the MAX for this column, over several minutes) is always below 1ms then I think the warning is definitely bogus and can be safely ignored. If you see peaks above 5ms then *maybe* that's what triggers the warning? If it's above 20ms then I think it's worth investigating, for instance try and turn off every program you can, or keep iostat running and try to identify when peaks occur, and what is running at the same time.
A little bit of noise is normal (especially if some writes occur, as they occasionally trigger GC in the SSD), trouble is if you see comparatively high latency for several seconds consecutively.
In any case, if you only see a warning and feel no problem with the game, then you're probably doing fine.