Re: [Discuss-gnuradio] scheduler internals

[Dimitris Symeonidis]

Thank you, Eric

Dimitris Symeonidis
"If you think you're too small to make a difference, try sleeping with
a mosquito!" - Amnesty International



On Mon, Apr 6, 2009 at 17:24, Eric Blossom <address@hidden> wrote:
> On Mon, Apr 06, 2009 at 04:14:21PM +0200, Dimitris Symeonidis wrote:
>> I have a flowgraph that is saturating my CPU, causing underruns.
>> I would like to find out the block (i.e. thread) that is loading the
>> cpu most heavily, in order to see if there's anything I can do to make
>> it lighter (and avoid having to try it on a more powerful system).
>> I have run "top" and pressed "H" to show threads, and see a lot of
>> "python" threads, most of them under 10% cpu load, and only one of
>> them at 49% cpu load, so that one is likely the culprit.
>> Is there some way to extract this information from the GnuRadio scheduler?
>>
>> Thanx
>>
>> Dimitris Symeonidis
>
> Try using oprofile.
>
> We'll eventually add per-block performance statistics, but that's
> pretty low on the priority list at this point.
>
> Eric
>