What kind of performance/speed issue are you experiencing?
· Tracks take a long time to play
Please try to reboot your Roon Server
· Yes, rebooting helps, but the issue returns after some time
Please try to reboot your networking gear (Router/Switches/etc.)
· No, the issue is still the same even after a reboot
Is there any change in behavior if you try to navigate to Roon Settings -> Library and set both Background and On-Demand Audio Analysis to Throttled or Off?
· No, the issue is still the same
Does the issue happen on multiple Roon Remotes (controllers) or just one?
· Issue happens on multiple remotes
Router Domain Name System (DNS) change
· I was able to change my router's DNS servers but it did not help
What is the operating system of your Roon Server host machine?
· Roon Optimized Core Kit (ROCK)
Timestamp of issue occurrences
· Almost exactly 3 days after turning on the server, last time it happened was May 17th, 2026 at ~07:00PM.
Describe the issue
Since April Roon ROCK gets extremely slow loading cloud tracks, Tidal, but only when the server been online for 3 days. ROCK is responsive and works fine when playing local files. After 3 days it takes up to 60 seconds to load Tidal tracks, and sometimes the Tidal page in Roon app takes very long time to load. While that page loads no playback starts, eg. I press play on a track, it starts loading and then I go to the Tidal page and it loads. The playback starts when the Tidal page is loaded, nothing happens before. Rebooting ROCK makes the system responsive for another 3 days.
I have tried this, but non solves the slow core issue: *Rebooting ROCK and router. *Changing DNS server. *Static IP and client specific DNS. *Installing a fresh version of RoonOS and database. *Resetting BIOS settings, I had it set to silent mode and turbo mode off.
Describe your network setup
Public IP, Asus RT-AX86U, ROCK wired directly to the router
Thanks for the detailed write-up! Sorry to hear you’ve been struggling with overall performance after letting your server run for a few days before another reboot.
Based on your description, it sounds like you’re suffering from some known memory-related issues our development team is actively working on optimizing.
The good news is that this is priority work on our end and our team is working hard to get these optimizations finished and released to you via a future Roon update.
That said, we don’t have any immediate next troubleshooting steps to try, other than a daily reboot of your Roon Server. A few things you could do to slow the the degraded performance would be:
Disable zones you don't regularly use in Settings → Audio could help reduce the memory footprint
Perform an Image cache clear from your Roon Settings > Library every few days
Thanks for your ongoing patience while we continue to work on a solution!
Upgrading to 32GB of RAM is a great proactive step and will certainly give your ROCK installation a lot more breathing room. It makes perfect sense that the system feels snappier right out of the gate!
To address your earlier question about whether more memory will solve the issue: adding RAM essentially gives Roon a much larger “bucket” to work with. Because the underlying software behavior our team is actively optimizing involves how memory is managed and released over time, this larger bucket will take much longer to fill up.
What to expect moving forward: You will likely see that the 3-day slowdown gets pushed out significantly—perhaps to a week or more—or the extra hardware overhead might just be enough to keep things running smoothly indefinitely until our development team releases the official optimization patch.
Please continue to monitor the system’s performance over the next few days. We would love to hear an update from you once you pass that 3-day mark to see how the new hardware handles the load. Happy listening!
Wanted to follow up on this and see how the upgraded 32GB of RAM has been holding up on your ROCK system. Have you made it past that three-day mark, and if so, are you still seeing the slowdown, or has the extra memory kept things running smoothly? WE also released a new Roon update to help with memory management, so we’d love to hear what you’re seeing, thanks.
The core slowed down after 3 days just as before. However, it got much faster after upgrading to v. 2.67. It has been working as it should for 2 days. Will update here if it keeps working past the 3 days mark.
Thanks for the update! I do still believe the optimizations our development team is actively working on will help your case, even with the added RAM you’ve upgraded.
Until then, your best bet is to perform a Roon Server reboot whenever you feel performance lag. I realize this is less than ideal, you have my apologies for that, and thanks again for your ongoing patience while our team continues to push to get these updates released to you.
The system is not slowing down as before anymore after the 3 day mark. However, the system reboots after 3-4 days instead. It is probably crashing due to something and bios makes it booting again. If you have not implemented auto-boot after 3-4 days ofcourse.
I’m really sorry to hear that! From a fresh diagnostic report, the pattern is consistent: the server doesn’t log any crash message or exception before dying, the log just stops abruptly. This strongly points to an external kill (watchdog, OS-level OOM killer, or RoonOS’s own process supervisor) rather than an internal exception.
It shouldn’t be much longer before these updates are available to you!
The system did not crash this time but got extremely slow loading anything after 4.5 days. This is very sad, before I never had to do anything to the Core. It ran without hick-ups for months and the only reboot that had to be done was when it was promted to do so after an software update. What happened to the Roon software this spring that introduced this bug to a system that worked flawless before?
Glad to hear that the crashing behavior subsided, even though there is still additional slowness. I am hoping that this can be resolved as well with our next Roon update that was just released to Early Access. Please feel free to give our latest Early Access release a try if you wish, or wait for the release to make it into production:
