[Top][All Lists]

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

Re: [Discuss-gnuradio] gnuradio-companion and multithreading

From: Marcus Müller
Subject: Re: [Discuss-gnuradio] gnuradio-companion and multithreading
Date: Wed, 21 Jan 2015 17:06:03 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0

Hi Andreas,

GRC is already as multithreaded as GTK applications can generally be --
I think the bottleneck here is really your Bananapi's CPU, its RAM and
its graphics card driver.
To be honest, I generally consider the Raspberry Pi and similar devices
to be embedded ones with hardware that underwent optimization for
exactly this application -- low cost embedded media playing linux GPIO
bitbanging computing. Not general purpose GUIs like the GRC.

Generally, the most sensible approach to using such devices with GRC I'd
say is to run GRC on your "real" PC, and transfer over the resulting
python program to your embedded device. Please don't expect wonders from
the signal processing performance of a dual core ARM processor --
there's only so much FLOPS you can get out of silicon...

Best regards,

On 01/21/2015 04:47 PM, Andreas Ladanyi wrote:
> Hi,
> iam testing gnuradio-companion editor on the Bananapi LUbuntu. When i
> am editing a block or drawing a block i recognize in top that the
> python process has a 100% CPU (i have 2 CPUs) load. The
> gnuradio-companion editor reacts very slow.
> Is it possible to tell the editor or python to use 2 CPUs ? I could
> remember that each gnuradio block in a project is one thread when
> running an compiled grc project so it seems to possible in general.
> 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]