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 don't know how to do this
What is the operating system of your Roon Server host machine?
· Roon on a NAS (Synology, QNAP, ASUSTOR)
Timestamp of issue occurrences
· July 10, 2026 8:00 PM
Describe the issue
Playing a track whether from Tidal or my local library (Synology NAS) can take almost 30 seconds. The same slow behavior exists when adding an album to my library.
2.70 server and remotes (iPadOS and macOS). Restarting the server (Container Manager on Synology) temporarily resolves this but issue will return overtime. I’m not even close to consuming significant system resources. Additionally, I will get “file not found” errors when removing something from my Library, and will have to go to the Tidal app in macOS to remove an album and then restart my server again.
Intermittent delay before playback starts, plus the file not found errors on library removal, makes me want to look at the Roon Server database and the Synology setup together.
Since restarting Container Manager helps for a while, there may be a server-side process or storage access issue that builds up over time. A few things would help us narrow it down:
Is the Roon Server container using an SSD volume on the Synology, or is the database stored on a mechanical disk or network share?
How large is the music library, roughly in albums or tracks?
Is the Synology connected to the XB8 by wired Ethernet?
We’d also like to review diagnostics around the time this happens. We will enable diagnostics on your account, and the next time you see the delay, please note the exact local time, date, and what you were trying to play or remove, then let us know here.
Reply with those details and we’ll take the next step from there.
We looked into what you flagged, and we do think it’s the same family of issue: garbage collection pauses in the Roon Server process building up over time and briefly stalling things. In your logs, the server’s memory footprint climbs steadily over roughly a day and a half of uptime, and we can see a playback stutter on your Living Room zone right after one of those heavier pauses, which lines up with the slowness you’re describing on both Tidal and local library playback.
We’ve added your case to the report R&D already has open on this. There’s no confirmed timeframe yet, but we expect a fix in an upcoming release.
In the meantime, since restarting Container Manager helps for a while, it’s worth automating that instead of doing it by hand. Synology’s Task Scheduler (Control Panel > Task Scheduler) can run a scheduled script to restart the Roon Server container on a set interval, for example once a day overnight. The exact steps depend on your DSM version and how the container is set up, so if you’d like a hand with it, please let us know your container or project name and we’ll walk through it with you.
If the issue is still there after the next Roon Server update, please open a new thread and reference this one (ref#85UPKH) so we can pick up from here.
Here’s a walkthrough for the daily restart, DSM 7.4:
Open Control Panel > Task Scheduler.
Click Create > Scheduled Task > User-defined script.
On the General tab, give it a name like “Restart RoonServer,” and set User to root (required for the script to control containers).
On the Schedule tab, set it to run daily at a time you’re not likely to be listening, overnight is usually best.
On the Task Settings tab, paste this into the User-defined script box:
docker restart roonserver
Save it, and it’ll run automatically going forward. You can also right-click the task and choose “Run” to test it immediately, then check in Container Manager that the container’s uptime has reset.
One thing to confirm: in Container Manager, please open the Container tab (not Project) and check the exact name listed there for your RoonServer container, it may be exactly “roonserver” or have a suffix like “roonserver-roonserver-1.” Please let us know that name so we can make sure the command above targets the right one.
As an additional option alongside the scheduled restart, you could also switch to our 2.71 Early Access build, which already includes the memory/GC improvements we mentioned. Since you’re on Docker, this is just one line in your Compose file: add ROON_INSTALL_BRANCH=earlyaccess under environment, then restart the container for it to take effect. One important note before doing this: please create a fresh Roon backup first. Early Access builds can include database changes that aren’t compatible with Production, so if you ever switch back, you’d want that backup on hand.
Either approach (or both together) should help in the meantime while R&D works on continuous improvements in this area.
Hi @yuhyuhariana, just a quick check-in: have you had a chance to try the suggestions above? We’re here to help if you run into any issues. Whether the problem is solved or not, we’d love to hear back from you. This thread will close automatically soon, but you’re welcome to reopen it anytime through the Technical Support form:
Please take a look at my logs around 6:09 PM on July 22. My CPU is being cooked and I’m just sitting here not playing music at the moment or browsing Roon.
Thanks for the follow-up! We haven’t yet pushed the additional optimizations over to Production yet, so it’s expected you’d still be experiencing the same behavior until this happens.
We’re going to mark this thread as a ticketed development item and remove the topic timer. Please keep an eye on the Software Release Notes category where we’ll be announcing the relevant changes and improvements.
The associated work is progressing through the queue. There are a few related improvements that will be included over the next several Roon updates, although this work hasn’t yet been finalized.
