[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Testing an GRC project runs nearly 200% CPU

From: Marcus Müller
Subject: Re: [Discuss-gnuradio] Testing an GRC project runs nearly 200% CPU
Date: Fri, 16 Jan 2015 00:58:41 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0

Hello Andreas,

you never need a throttle block when you have hardware that
limits/defines your real-world sampling rate; in your case, it's your RF
hardware and your sound card.
Aside from things like implicit resampling in the audio card driver
infrastructure, it's absolutely possible that your bananapi is simply
not performant enough to do GUI, signal processing and audio playback at
The question is: Does the same application work sufficiently well on a
fast PC? Do you see any over- or underrun warnings on your console?


On 01/15/2015 10:38 PM, Andreas Ladanyi wrote:
> Hi,
> iam testing an UKW Radio Receiver GRC project (gr-rds) on bananapi.
> The application starts. The tuned radio station sounds clicking.
> Changing any parameter in the GUI is very difficult/slow.
> top tells me a memory usage about 20 %. CPU usage is nearly 200 %
> (bananapi has 2 CPUs). At any webside i read that working with no
> throttle blocks could run a CPU to maximum. In my project which iam
> testing i see no throttle blocks. I am not sure if that could be the
> reason because iam working on the bananapis real hardware ?
> Is there something wrong with the sample rate ?
> Andreas
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

reply via email to

[Prev in Thread] Current Thread [Next in Thread]