Rainbow.9137

It's nearly 70 GB. The best solution is to move it into SSD, trust me. OK, you had done that. Maybe the develop team should design a bigger memory pool to prevent repeat load/unload action. In disassembly, the Processor count can be identified. So why not physic memory size.

I hope that the developer can use some profiler tool, such as Intel VTune Profiler. Old code need to be refreshed and refit. Oh, I also find some ASM code in the program, seeming to transform matrix, so cool and effective.

What I MEAN is that if there haven't too much work to do, the better solution is to call sleep rather than use spin lock. In total 1515s CPU time, effective time is 711s, the SPIN Time is 802s. The program is NOT CPU-HEAVY. In fact, It's SPIN-HEAVY. THAT is what I want to express or describe. By the way, it seems that using NVIDIA panel to limit frame better than using the option in game.

Just like the title, I have measured GW2 program. The result contains hotspots, threading and topdown. hotspots: yimitool.com/i/2023/03/16/uga9dn.png ; threading: yimitool.com/i/2023/03/16/ugahun.png ; topdown: yimitool.com/i/2023/03/16/uj6m82.png ; (https://) pre-fix