Scheduler Overload
Simon Brown • October 7, 2024
Too Many Entries
July 15th, 2024: Recently I was looking at issues with very large Scheduled Recording databases (thousands of entries), as scheduled runs were being missed.
As part of this work, I reduced the amount of information written to the logfile, this could have been:
- Clogging up the main thread processing, also increasing the memory footprint.
- Delaying the start of a recording.
I'm glad to say this solved the problem.

SDR Television Found and fixed an unused massive memory allocation (up to 10GB), may have caused systems to freeze. Fixed fatal bug in matched filter array allocation. Changed the default transmit bandpass shaping filter roll-off to 0.20 in transmit and receive. Please look at the images below and apply the change. SDR Pluto Now show the AGC gain and RSSI. Added Default link to select the recommended gain - Fast Attack, 0dB visual. Known Problems Add support for tracking transmissions with (?) non-standard PCR data, example is G8GKQ. Using Pluto & variants, sensitivity is not as good as a NIM (hardware tuner). Will compare with SPECTRAN ECO in a week or so.

After too much grief, I've decided to stop using Wi-Fi to connect the small NUC systems in the computer room to my network: DX Cluster (Ubuntu) SDR Server (Windows) User Forums (Windows) These servers are in constant use, causing the wireless transmitter on my TP-Link AX50 to fail. By switching over to a wired network there's less demand on the wireless transmitter and the whole network has become far more reliable. In future I will only use Wi-fi when there's no alternative. I'm keeping a spare router ready just in case the AX50 fails.