Re: [GD-General] profiling multi threaded applications

[Andras B. <and...@gm...>]

Pretending that this is not an option, are there any other possibilities?


Christian Laforte wrote:
> If possible, design your architecture so that your threads can work in a
> lockstep mode, with one central mutex controlling which thread is running at
> any given moment. That way you can at least get a partial profile and
> optimize each thread individually.
> 
> This type of design can also prove very useful to debug deadlocks.
> 
> Hope that helps a bit,
> 
> Christian Laforte
> www.feelingsoftware.com 
> 
> 
>>-----Original Message-----
>>From: gam...@li...
>>[mailto:gam...@li...] On Behalf Of
>>Andras Balogh
>>Sent: Wednesday, July 20, 2005 10:36 AM
>>To: gam...@li...
>>Subject: [GD-General] profiling multi threaded applications
>>
>>I was about to add a simple profiler into our engine, but I've just
>>realized that the usual hierarchical profiler that measures the time for
>>a chunk of code won't cut it, in a multithreaded application.
>>
>>I understand that even when I have a single threaded app, there are
>>usually several other applications are running in the background, but
>>mostly they are all idle, so it's just noise. But in this case, I would
>>have multiple, heavily working threads. If the OS switches back and
>>forth between these threads all the time, then how is it possible to
>>make accurate, or even just usable measurements??
>>
>>Thanks,
>>
>>Andras