|Subject:||Re: [Discuss-gnuradio] Testing an GRC project runs nearly 200% CPU|
|Date:||Fri, 16 Jan 2015 09:43:30 +0100|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0|
that's kind of interesting, because if it works on a PC, I'd say it's a performance issue; if you don't see aU (audio underruns) or some osmosdr warnings, then I'd say it's not.
What one does in this situation is both running a process-based cpu usage tool; I recommend "htop" (which is like top, but actually a lot nicer). Do you have another process suddenly consume CPU? Does it look like it's pulseaudio (that would be the implicit audio resampling issue)?
If, what I presume, you only see two python processes consuming 100% each, you will need to dig deeper. There's a tool called "perf" , which, when run as "perf top" as root will let you introspect CPU usage per method, including kernel routines.
Both perf and htop are available as packets for many Linux distributions.
On 01/16/2015 09:27 AM, Andreas Ladanyi wrote:
|[Prev in Thread]||Current Thread||[Next in Thread]|