On Fri Oct 11 14:47:40 2024 +0000, Rémi Bernon wrote:
If you want to run benchmarks you should use `WINEDEBUG=-all`, anything else is pretty much meaningless. In particular, doing WINEDEBUG=err-d3d will give even worst results, because it allows d3d log level to be changed dynamically through the taskmgr, which means every trace will have to check if the level has changed.
The benchmark was only used as an example and easier to test than the full game (Final Fantasy XI Online), which has the same issue with about 10,000 lines of output coming in from err d3d now, as also described in bug 57207 [1], and it was a bit surprising that 'err-d3d' would actually make things worse.
I does seem like it was to be expected, but I have not bumped into that effect before, when actually disabling things instead of the reverse.