Low FPS on the latest versions.
Hi.
Can I get version 1.333 for installation on an sd card? Or roll back? I experience serious FPS problems when users launch LMS Filter and more. There were no such problems on version 1.333 or lower. Or it was uncritical. Now, on the 8 channels configuration, FPS is sometimes = 1. That is, a waterfall is constantly standing. WSPR and similar extensions are not used. I even turn off the GPS to unload the processor. On the configuration of 4 channels there is also a problem, but not so critical. I have 4 kiwi in different places and everywhere a similar problem.
Thanx for project!
Can I get version 1.333 for installation on an sd card? Or roll back? I experience serious FPS problems when users launch LMS Filter and more. There were no such problems on version 1.333 or lower. Or it was uncritical. Now, on the 8 channels configuration, FPS is sometimes = 1. That is, a waterfall is constantly standing. WSPR and similar extensions are not used. I even turn off the GPS to unload the processor. On the configuration of 4 channels there is also a problem, but not so critical. I have 4 kiwi in different places and everywhere a similar problem.
Thanx for project!
Comments
With v1.357 (latest) a Kiwi configured for 8-channels shows waterfall frame rates ("WF" on "Stats" tab of user control panel) of med=13 and fast=23 fps. This is zoomed all the way out, two users connected and one WSPR extension running. But with no antenna connected so the WSPR decoder phase doesn't run for any amount of time.
Remember that the WSPR decoder loads the Beagle CPU very heavily and causes the waterfall priority to drop decreasing its frame rate. Do you have channels configured for WSPR autorun? I found no changes when changing the LMS filter.
I went to an 8-channel Kiwi with one user connection and 3 WSPR autoruns. My WF on "fast" mode was only 2 fps during all but the last 15 seconds of the 2 minute WSPR window. During the last 15 seconds it went back to normal because that's when the WSPR decoders are stopped (assuming they are swamped with weak signals they are trying to process). That's how it's all supposed to work.
I checked a few other 8-channel Kiwis listed on sdr.hu and they all seemed fine. There is a way you can manually revert to an earlier software version via the admin "console" tab or a Beagle ssh/PuTTY connection. let me know if you'd like that info.
And further. On version 1.295 with 4 simultaneous connections (for example, lsb / usb modulation) fps 40 or more. On some not very old versions there were even 50! I dont remember which ones. On the latest software versions with 4 simultaneous connections, FPS does not rise above 25...27. All tests without LMS Filter. GPS is on.
kiwi.waterfall process no. John, do you want to connect via ssh, or do you just need the addresses of my problem receivers?
If anything, the addresses above.
On all the kiwis next to me I observe these problems.
Only "kiwid" seems to be taxing the CPU but hard to say if actual load much different on/off (from "top").
Stu
I found out that LMS Filter affects all versions. Written above in the text.
Am I comparing with older versions? More on this below. Because LMS Filter is not the only problem. Just in recent days, 2 comrades came up right away with these settings (denoiser + autonotch). And the waterfall almost did not work. previously did not pay attention that this is possible. And I began to figure out what was wrong. And since they come to me not just to check, but to monitor for a very long time (!), this is unacceptable. Well, with the 333 version or a little later, FPS decreased, even without using LMS. Command top: besides kiwid, nothing seriously takes resources. 2 receivers online. Easy to check. You need to load all the channels.
PS: for John: I do not use WSPR decoders.
I can see the slow down even with only two connections with LMS and Notch, I was not disagreeing with anyone.
I can barely think and type at the same time (look up the meaning of numpty then add a turbo and you have powernumpty).
Stu
For these Kiwis please tell me:
I observe the following (at zoom levels 0-9; z10-13 slows down due to increased processing) So GPS acquisition has a big effect on waterfall fps. When running it also makes the additional load of LMS have a large impact on fps. I did not expect this.
So a few things are now clear:
GPS antenna connected.
GPS reception marginal or average.
About FPS: I meant the total value, of course. Not the first day an engineer Yes, I suspected that it was GPS. And immediately turned it off. In a e-mail I wrote about this. With GPS disabled, FPS is normal, but still does not reach a bit to old versions.
But with LMS Filter also need to do something. By the way, I really like Denoiser in the Amplitude Modulation mode, this is really a cool thing. I set my optimal settings when listening to radio pirates, for example.
I haven't looked at it, but it is possible the denoiser and auto-notch can be moved from the Beagle to Javascript running on the browser. Assuming the browser is running on a decent device (desktop pc or recent mobile device) the performance should be sufficient to support it.
But let the existing LMS Filter work in the same variant as now. Let them be available at the same time. Only the option using Beagle resources will not be available for everyone.
Thank you.