|Subject:||Re: [Discuss-gnuradio] unexpected underruns|
|Date:||Wed, 2 Aug 2017 16:37:20 +0200|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0|
Ok, there's something fishy here. That rate (without the USRP Sink) is ridiculously low. Can you replace the file_source with a null_source? That way, we can rule out storage as the bottleneck.
The probe_rate does nothing but just count how many items fly by, and then send a message at its output port every update period. The message_debug just prints messages.
If it's not storage: are you perhaps running in a powersaver
mode? Even so, the rate would be too low. I really don't know
what's going wrong here. Run your flow graph, run "top" in a
terminal, check that the python process and its spawned child
threads really consume most of the CPU. If that's not the case,
you've got something else eating away on your CPU.
On 08/02/2017 04:22 PM, Rui ZOU wrote:
|[Prev in Thread]||Current Thread||[Next in Thread]|