Forum: GNU Radio scheduler internals

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
C0ba64b9e5a62ed77295b79b63ab87c0?d=identicon&s=25 Dimitris Symeonidis (Guest)
on 2009-04-06 16:16
(Received via mailing list)
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
"If you think you're too small to make a difference, try sleeping with
a mosquito!" - Amnesty International
745d8202ef5a58c1058d0e5395a78f9c?d=identicon&s=25 Eric Blossom (Guest)
on 2009-04-06 17:33
(Received via mailing list)
On Mon, Apr 06, 2009 at 04:14:21PM +0200, Dimitris Symeonidis wrote:
>
> 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
C0ba64b9e5a62ed77295b79b63ab87c0?d=identicon&s=25 Dimitris Symeonidis (Guest)
on 2009-04-06 18:00
(Received via mailing list)
Thank you, Eric

Dimitris Symeonidis
"If you think you're too small to make a difference, try sleeping with
a mosquito!" - Amnesty International
This topic is locked and can not be replied to.