Closed VasilisThePikachu closed 6 months ago
The setting is somewhat useful; dynamic PGO does add a bit of startup time to the client, due to how large the assembly is. Though making it default would probably be a good idea.
The setting is somewhat useful; dynamic PGO does add a bit of startup time to the client, due to how large the assembly is. Though making it default would probably be a good idea.
I would take client performance over a little bit extra startup time
The extra startup time is not insignificant on lower-end hardware
How much longer is it? And how low end are we talking?
The extra startup time is not insignificant on lower-end hardware
Do you have numbers on this? And are these up-to-date with .NET 8? I know they've had tons of improvements with OSR and similar.
We do not, admittedly! Plus it's been quite a while since we last poked at it ourself (and coincidentally it's been quite a while since we had a computer where it actually mattered). It's something that should probably be benchmarked proper.
We could turn the checkmark into something that disables Full PGO instead, and clearly mark it as such.
So this is on decently good hardware. But having the option turned on or off does not impact startup time at all.
About 9 second from launch to game
I sadly don't own any too old hardware
Some more findings:
MacBook air m1 (battery saving mode to give it a disadvantage)
With PGO enabled: 30 seconds to get from launcher to game With PGO off: 25 seconds
Windows laptop with an intel i5 5200u, 8gb ram PGO on: 35 seconds PGO off: 30 seconds
Seems all around on weak hardware it's about 5 more seconds for launch.
As far as I know, no one has experienced an issue with it. May as well remove some clutter. And make sure its on by default