Hey there,
I'm experiencing some performance problems with wined3d. The affected game is FEAR (demo does the trick). At first I thought it was related to running the demo on my Intel i965, but I got the same problem running the demo on my Radeon HD4750@r600g.
If anyone wants to test this himself: http://www.gamershell.com/download_10167.shtml Performance collapses (kinda SW rendering level) after exiting the first underground section. My guess is that the water plane rendering is causing the issue.
So anyway, I wanted to profile this one, but gprof doesn't seem to work so well with wine. I tried to only compile wined3d with -pg, but this doesn't seem to have any effect. At least I don't get any gmon.out after the process exits.
What is the recommended way of profiling wine components? oprofile?
Thanks, Tobias
On Tue, Feb 22, 2011 at 8:53 PM, Tobias Jakobi liquid.acid@gmx.net wrote:
What is the recommended way of profiling wine components? oprofile?
See http://wiki.winehq.org/Performance
oprofile works well if things are cpu bound, or for illustrating cases of redundant calls. If oprofile shows a lot of time in video drivers, you could try gDEBugger mentioned on the above wiki page to gain some insight.
Jeff
In case of Intel make sure you use drivers with debug symbols :) Yeah, you could use oprofile, but for some quick and easy profiling sysprof can be easier and much quicker.
Roderick
On Tue, Feb 22, 2011 at 2:55 AM, Jeff Zaroyko jeffzaroyko@gmail.com wrote:
On Tue, Feb 22, 2011 at 8:53 PM, Tobias Jakobi liquid.acid@gmx.net wrote:
What is the recommended way of profiling wine components? oprofile?
See http://wiki.winehq.org/Performance
oprofile works well if things are cpu bound, or for illustrating cases of redundant calls. If oprofile shows a lot of time in video drivers, you could try gDEBugger mentioned on the above wiki page to gain some insight.
Jeff
-
Jeff Zaroyko -
Roderick Colenbrander -
Tobias Jakobi