Profiling wine

[Mike Hearn]

Hi,

Is there any way to get measurements of where Wine is spending most of
its time? I have a problem where typing text into the WebBrowser control
is incredibly slow, but don't really have a clue where to start looking.
A profiling tool would be handy about now......

thanks -mike

[Jeremy White]

Hey Mike,

Charles and Mike did a fair amount of work to submit a
patch to Wine to enable a profiling mode.

Sadly, Mike is on vacation this week, so i'm not sure if he's
around to help out.

But if you look through the archives (I think Mike mailed it in),
you should find it.

We'd really like to have other folks using this code...

Cheers,

Jeremy

Mike Hearn wrote:
> Hi,
>
> Is there any way to get measurements of where Wine is spending most of
> its time? I have a problem where typing text into the WebBrowser control
> is incredibly slow, but don't really have a clue where to start looking.
> A profiling tool would be handy about now......
>
> thanks -mike

[Mike Hearn]

On Tue, 2003-07-29 at 03:47, Jeremy White wrote:
> But if you look through the archives (I think Mike mailed it in),
> you should find it.

Yup, found it, but looking through the code it seems Mikes initial
evaluation (i missed bits and it doesn't work) is accurate. Is Charles
around? If so it'd be good to get this patch into WineHQ, more and more
bugs these days seem to be along the lines of "wine is too slow". I also
have some questions, like what exactly WINE_NO_PROFILE does (it's
defined to nothing....)

thanks -mike

[Lars Segerlund]

How about giving oprofile a spin ?

It is very good at pinpointing runtime hotspots. I just wanted to give 
a suggestion on how to get going with profiling right now without the 
need to wait for wineprofile functionality.

/ Lars Segerlund.

Mike Hearn wrote:
> On Tue, 2003-07-29 at 03:47, Jeremy White wrote:
> > But if you look through the archives (I think Mike mailed it in),
> > you should find it.
>
> Yup, found it, but looking through the code it seems Mikes initial
> evaluation (i missed bits and it doesn't work) is accurate. Is Charles
> around? If so it'd be good to get this patch into WineHQ, more and more
> bugs these days seem to be along the lines of "wine is too slow". I also
> have some questions, like what exactly WINE_NO_PROFILE does (it's
> defined to nothing....)
>
> thanks -mike

[Jeremy White]

> How about giving oprofile a spin ?
>
> It is very good at pinpointing runtime hotspots. I just wanted to give 
> a suggestion on how to get going with profiling right now without the 
> need to wait for wineprofile functionality.

I'm told (and have been persuaded of this), that Wine's internal
structures preclue a 'normal' profiler from working properly,
hence the need for a Wine specific one.

I know we toyed with adapting gprof to Wine semantics, but
decided, in the end, that was too hard and not worth it.
> > Yup, found it, but looking through the code it seems Mikes initial
> > evaluation (i missed bits and it doesn't work) is accurate. Is Charles
> > around? If so it'd be good to get this patch into WineHQ, more and more
> > bugs these days seem to be along the lines of "wine is too slow". I also
> > have some questions, like what exactly WINE_NO_PROFILE does (it's
> > defined to nothing....)

charles spam hunters should not know to add an at codeweavers.com.

Cheers,

Jeremy

[Ove Kaaven]

tir, 29.07.2003 kl. 13.55 skrev Jeremy White:
> > How about giving oprofile a spin ?
> >
> > It is very good at pinpointing runtime hotspots. I just wanted to give 
> > a suggestion on how to get going with profiling right now without the 
> > need to wait for wineprofile functionality.
>
> I'm told (and have been persuaded of this), that Wine's internal
> structures preclue a 'normal' profiler from working properly,
> hence the need for a Wine specific one.

Then again, oprofile is not a normal profiler, it's a kernel-based one.
I've tried it, it "works", but it seems that it requires a 2.5 kernel in
order to be really useful (it's not able to generate call graphs with
2.4)

[Mike McCormack]

Hi Mike,

When compiling the profiled build, the configure script defines the 
Makefile variable PROFILE_CFLAGS to contain:

-DWINE_NO_PROFILE="__attribute__((no_instrument_function))"

When we're not using the profiler, WINE_NO_PROFILE is defined to 
nothing, and thus has no effect.

Mike

Mike Hearn wrote:
> Yup, found it, but looking through the code it seems Mikes initial
> evaluation (i missed bits and it doesn't work) is accurate. Is Charles
> around? If so it'd be good to get this patch into WineHQ, more and more
> bugs these days seem to be along the lines of "wine is too slow". I also
> have some questions, like what exactly WINE_NO_PROFILE does (it's
> defined to nothing....)
>
> thanks -mike