Song history overloading MariaDB

[carlojou]

Installation Method

Docker Installation

AzuraCast Release Channel

Stable Channel

Current AzuraCast Version

0.19.5

What happened?

Hello,

We've noticed that song history in particular seems to hammer the MySQL server if you have multiple stations running - for instance:

26509098 | azuracast | localhost | azuracast | Query   |    0 | Sending data    | SELECT s0_.station_id AS station_id_0, s0_.playlist_id AS playlist_id_1, s0_.media_id AS media_id_2, |    0.000 |
| 26509099 | azuracast | localhost | azuracast | Query   |    0 | Sending data    | SELECT s0_.station_id AS station_id_0, s0_.playlist_id AS playlist_id_1, s0_.media_id AS media_id_2, |    0.000 |
| 26509100 | azuracast | localhost | azuracast | Query   |    0 | Sending data    | SELECT s0_.station_id AS station_id_0, s0_.playlist_id AS playlist_id_1, s0_.media_id AS media_id_2, |    0.000 |
| 26509101 | azuracast | localhost | azuracast | Query   |    0 | Sending data    | SELECT s0_.station_id AS station_id_0, s0_.playlist_id AS playlist_id_1, s0_.media_id AS media_id_2, |    0.000 |
| 26509102 | azuracast | localhost | azuracast | Query   |    0 | Sending data    | SELECT s0_.station_id AS station_id_0, s0_.playlist_id AS playlist_id_1, s0_.media_id AS media_id_2, |    0.000 |
| 26509103 | azuracast | localhost | azuracast | Query   |    0 | Sending data    | SELECT s0_.station_id AS station_id_0, s0_.playlist_id AS playlist_id_1, s0_.media_id AS media_id_2, |    0.000 |
| 26509104 | azuracast | localhost | azuracast | Query   |    0 | Sending data    | SELECT s0_.station_id AS station_id_0, s0_.playlist_id AS playlist_id_1, s0_.media_id AS media_id

We're not sure what to do here, this can sometimes lock you out of the UI completely as MySQL tries to catch up with all the queries. It spawns 30-40+ sql queries at once.

There is also no way for us to disable song history either, we can only reduce the amount of history it maintains but that only helps with space. We already have it set to the minimum (14 days) but the issue persists.

Please do let me know if theres anything we can do here to fix this, perhaps have an option to disable it entirely for bigger installs.

Thank you!

Relevant log output

No response

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

Thank you for your bug report, this issue has been closed due to inactivity. Should this issue persist, please re-open the bug report.