Savegame load performance? Typical vs. ideal times? System load?
I'm a bit puzzled. I haven't played in a while and can't really test it on my old Intel system without major hardware juggling anymore, but I seem to remember an SSD load time of 12 seconds for a savegame, with HDD more like 30-45. Now I migrated my Win7 to a Threadripper system and am getting savegame loads of ~30 seconds from SSD, regardless of whether it's an early or late savegame. But videos I found show the same.
Also, when checking system stats, even if a load process has been system-cached, resulting in pretty much no data loaded from SSD, it still takes that long, with CPU load very low at least on my new system. Could it be that W3 savegame loading is load capped? That it only uses one thread or such and might not even make full use of it? It would be weird, since W3 is a CPU-heavy game once it has loaded into the world. I'm wondering what it is doing all the time while I'm waiting on the load screen, seeing no SSD reads and 7% (Threadripper) CPU load.
AFAIU a major part of it would be decompression of textures and other sources, but how could that not be parallelized super-easily?
Basically, a bit polemically, when loading a savegame my computer has nothing to do and nothing is happening.
(Little side note: Disabling HPET in Windows really solved some nasty DPC latency issues on my AMD system causing audio dropouts, floaty cursor, stutter in video recording and gaming and such..)
I'm a bit puzzled. I haven't played in a while and can't really test it on my old Intel system without major hardware juggling anymore, but I seem to remember an SSD load time of 12 seconds for a savegame, with HDD more like 30-45. Now I migrated my Win7 to a Threadripper system and am getting savegame loads of ~30 seconds from SSD, regardless of whether it's an early or late savegame. But videos I found show the same.
Also, when checking system stats, even if a load process has been system-cached, resulting in pretty much no data loaded from SSD, it still takes that long, with CPU load very low at least on my new system. Could it be that W3 savegame loading is load capped? That it only uses one thread or such and might not even make full use of it? It would be weird, since W3 is a CPU-heavy game once it has loaded into the world. I'm wondering what it is doing all the time while I'm waiting on the load screen, seeing no SSD reads and 7% (Threadripper) CPU load.
AFAIU a major part of it would be decompression of textures and other sources, but how could that not be parallelized super-easily?
Basically, a bit polemically, when loading a savegame my computer has nothing to do and nothing is happening.
(Little side note: Disabling HPET in Windows really solved some nasty DPC latency issues on my AMD system causing audio dropouts, floaty cursor, stutter in video recording and gaming and such..)
Last edited by a moderator: