![]() They also don'tr have any effect vs unedited config.wtf.Įven so, there's a small improvement in demanding areas on my PC, maybe 60 fps vs 48 or so on the most demanding area I've found.On the PTR, those values are default when DX12 is enabled. 6+ core processors are becoming commonplace now so a sloppy implementation can ruin things for many.ĭon't stick after game restart for some reason. ![]() But seeing this clear performance change when playing with affinity got me alarmed. I am not saying I'm drawing any definite conclusions on how this will work out for all PCs as there are so many variables to think of, not only with hardware but also what activity in the game you are doing. ![]() My theory here is that anyone with more than a quad core should evaluate this for themselves come patch day and if you have a quad core with SMT (eg Ryzen R3 or older Core i7) it may be worth testing with forbidding WoW to access to more than one thread per core (as mentioned previously setting affinity to core 0, 2, 4 and 6 would achieve this). 4 cores were the sweet spot and simply allowing it access to just one more started showing live performance declines My finds were that limiting WoW to access only 4 (four) cores and absolutely only one thread per physical core (eg affinity set to core 0, 2, 4, 6) notably improved performance, reaching 100+fps in my scenario instead of 85 vs just letting the game run "al naturale", spreading across any core it wanted. This can be done through multiple ways but in my case I used the tool Process Lasso as it allows for changing on the fly (no restarts needed as opposed to setting it up with cvars in config.wtf) and was simple to use. For anyone not in the know it's when you manually forbid a program access to one or many cores or threads. Seeing as I have plenty of cores, I then started playing around with CPU Affinity. I picked a cozy spot in Dazaralor and noted around 75 FPS with DX 11 on and then about 85 with DX 12 enabled (game restarted in between). SET gxMTShadow "1"as this was seemingly a prerequisite for early PTR testing but didn't seem to make any difference for me, so I'm assuming it's all on by default now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |