Recommendations to lighten an instance that has been running for many months.

I've been using radioboss since 2018 (5.7.2.0) non-stop. At first, when loading playlists of material, playback was immediate, but as time went by this became slower. It took 1 second to play the first material. Currently, it sometimes takes up to 3 seconds, generating up to 90% CPU usage. Is it possible that there is some parameter that slows down the start? For example, the playback count? I have deleted log files and others but it does not make a difference. Is there anything that can be done? I have no problems with RAM usage or hard drive access speed.
I also have high priority enabled for the process.

For example, after the command execution, a call to an m3u file containing some playback materials follows (a few, no more than 15).

1732333453780.png
 
Last edited:
To ensure the maximum track startup speed, you should use the SQLite database option: https://manual.djsoft.net/radioboss/en/additional-information-storage.htm (there's also a sub-article about transferring information from one storage to another).

If you have been using RadioBOSS since version 5.7, it's likely that the additional information is configured to use the legacy APEv2 tag, and that's somewhat slower than SQLite (still, starting a playback should take like 100ms with this, and in case of SQLite it's under 50ms).

Please also ensure that you have Preload enabled in Settings, General, Advanced configuration, "Playlist - Preload ..." (it's on by default).
 
To ensure the maximum track startup speed, you should use the SQLite database option: https://manual.djsoft.net/radioboss/en/additional-information-storage.htm (there's also a sub-article about transferring information from one storage to another).

If you have been using RadioBOSS since version 5.7, it's likely that the additional information is configured to use the legacy APEv2 tag, and that's somewhat slower than SQLite (still, starting a playback should take like 100ms with this, and in case of SQLite it's under 50ms).

Please also ensure that you have Preload enabled in Settings, General, Advanced configuration, "Playlist - Preload ..." (it's on by default).

Ok. I just changed the configuration to SQLite. I'll see how it goes.
I don't really use the music library in my case. I just use Radioboss as a playlist player. I don't need the play count, or the last time it was played. Or any other additional data. Is there a way to disable those features?

(I think in version 5.7 there was no "advanced settings" option yet.)

The largest files I have in the configuration folder are these. Is it related? I don't know what data is in Encoderstats (I don't use it but I think it is recorded anyway).

1732590782296.png

1732591089410.png
 
I don't really use the music library in my case. I just use Radioboss as a playlist player. I don't need the play count, or the last time it was played. Or any other additional data. Is there a way to disable those features?
Those features can't be disabled, as those are the core functionality. Using SQLite does make it as light as possible so there's no overhead that you might notice. APEv2 is a lot heavier though as it requires modifying the music file each time it's started.

(I think in version 5.7 there was no "advanced settings" option yet.)
Maybe, it was added at some point to handle some special configuration needs.

The largest files I have in the configuration folder are these. Is it related? I don't know what data is in Encoderstats (I don't use it but I think it is recorded anyway).
EncoderStats store the listener numbers for the streaming servers. It does not affect playback performance in any way. PlayedTracks file stores the played file list for Track List repeat protection.
 
Back
Top