Re: [Discuss-gnuradio] diagnosing overflows

Hi philip,

to identify such bottlenecks, it's often a nice clue to know which block consumes the most CPU. I don't know it the Linux perf counters work well on ARM (simply haven't tried), but if they do: There's a program called perf. Usage in short

sudo sysctl kernel.perf_event_paranoid=-1
perf record -ag python yourflowgraph.py
perf report

Best regards,
Marcus

On 08/10/2017 03:28 AM, Philip Hahn wrote:

Sean - OK, I understand what you mean now, thank you - the overflow is not reported until the pressure hits the source block.

Cinaed - In this case it is not my flowgraph but gnss-sdr which I've run successfully on several platforms. In this case it is running on a Raspberry Pi 3. I anticipate hitting some roadblocks although reportedly it's been done before; I am trying to determine the current bottleneck.

thanks 

philip

On Wed, Aug 9, 2017 at 3:15 PM, Cinaed Simson <cinaed.simson@gmail.com> wrote:

On 08/08/2017 07:56 PM, Philip Hahn wrote:
> Folks,
>
>  Is there a way to diagnose which block first reports an overflow in a
> flowgraph?
>
>  In my particular instance I am running a flowgraph which is overflowing
> without pegging either RAM or CPU.

It could also be an error in the plumbing of your flowgraph.

-- Cinaed

>
>  Thank you,
>
> philip
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>


_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

_______________________________________________  Discuss-gnuradio mailing list  Discuss-gnuradio@gnu.org  https://lists.gnu.org/mailman/listinfo/discuss-gnuradio