Re: wined3d profiling

[Jeff Zaroyko]

On Tue, Feb 22, 2011 at 8:53 PM, Tobias Jakobi <liquid.acid(a)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