Open Psynosaur opened 9 months ago
Theory...
Perhaps reducing this load on the plutoSDR processor would resolve other IO related issues?
CPU's that are pegged at 100% and trying to cope with the rest of the Kernel instructions tend to favor finishing the threads and then triggering IO interrupts if needed to cope with the next set of instructions.
Could we please have more granular control over this?
The halving of the rate made the waterfall particularly slow, perhaps we could remove 1/4th the original speed or 1/8 ?
The CPU usage is much improved :)
Hi
500ks seems to be my pluto's limit for the settings below
after which at 1Ms the cpu usage on the pluto is mostly pegged at 100% and my stream has artifacts
Could we please have some analysis of which branches of execution within
pluto_stream
take up resources to perhaps optimize itPS. plugging in the Pluto to
USB
resolves this issue, but then, we loose all the analysis tools... So it might be network related.Regards