Performance degradation on Roon Rock after prolonged uptime (ref#R761T7)

What app are you having the slowness issue with?

· Roon

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?

· I only have one Roon remote to test with

Please try to restart your Roon Remote (controller) app

· No, the issue is still the same even after a restart

What is the operating system of your Roon Remote (controller)?

· Windows

Reinstall Windows/MacOS Roon Remote App

· No, I am still having the issue even after reinstalling

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

· The problem begins after a day of server uptime, regardless of the current time.

Describe the issue

Hello, the problem is this:
Roon Rock is installed on a NUC7i3 with 16GB of RAM. The database is on a 256GB SSD, and the tracks are on a 1TB HDD. The NUC is connected to the router via a gigabit Ethernet port. RoonOS version 2.1 (build 271) production, Roon Server version 2.65 (build 1653) production, and Roon on the computer version 2.65 (build 1653) production (64-bit).
The library is relatively small: 2,800 albums and 35,000 tracks,0 unidintified.
After loading the Roon Server, music plays normally, including local music or tracks from Qobuz. After a day of uptime, I started experiencing slowdowns: the Roon Remote interface takes noticeably longer to load, and playback is delayed: local tracks take 5-7 seconds, Qobuz tracks take 7-15 seconds, and Roon Radio can take up to half a minute.
I thought it was due to the RAM being full, because as soon as I restart the server, Roon comes back to life and responds to the play button almost instantly. I thought the problem would go away with the latest update, and after installing it, it did indeed improve noticeably, but after a day, the issue has been recurring for the second day.
I disabled background analysis, background tasks, and backups, but the problem reoccurs a day later and can only be fixed by restarting the server.
I'd like to figure out why Roon Rock turns into a pumpkin after a day of uptime =)
Or I'd like to add a scheduled automatic shutdown/restart feature; that would partially solve the problem. Unfortunately, the NUC can only be configured to turn on, not off =(

Describe your network setup

The gigabit internet is connected to a Keenetic Giga (KN-1801) router, which also has a Roon Rock server connected to it. The computer connects to the router and network via Wi-Fi 6 (5 GHz).

Hi @Atiss,

Thank you for your post. We’ve taken a look at logs to see what we can diagnose.

We see connections in logs to Roon’s cloud services timing out and re-requesting. TCP streams are dropping mid-response. Image downloads are failing entirely. We don’t see evidence of memory spikes. These symptoms are consistent with problems introduced by georestriction.

Most of Roon’s upstream services, including Qobuz, are not available in the geographic location associated with your account. Are you relying on a consumer VPN to use Roon?

This issue has nothing to do with my geographic location, as Qobuz is fully accessible here, without a VPN, and works perfectly in its native app! Roon is also fully functional. I also don’t use a VPN. Moreover, judging by recent open tickets, I’m not the only one experiencing this issue. Again, this doesn’t compare to the fact that a server restart is enough to restore normal operation, and it can work fine for 24 hours.

It’s been more than a day and a half since the last Roon server reboot (April 30, at approximately 7:40 PM local time).
Yesterday, I periodically returned to listening to music throughout the day, and everything was fine – minimal pauses between tracks, a responsive interface, and quickly loading cover art.

This morning, Roon on my computer started to lag. The start page is noticeably slower to load, I’ve noticed longer pauses between tracks, and sometimes cover art loads with a delay. Turning on Roon Radio takes 15-17 seconds, and switching between playing a local file and a file from Qobuz can take up to 10 seconds. While the issue isn’t critical and happens occasionally, I’m not rebooting the server so we can review yesterday’s and today’s logs.

Strange, since you are apparently located in Russia and that is not one of the countries where Qobuz is supported.

Where is Qobuz available? | Qobuz Help Center

Qobuz is fully available in Russia without restrictions. The only issue is with direct subscription payment.

This morning (May 3), performance deteriorated even further:

The homepage took about 15 seconds to load.

Tracks switch with a 7-15 second delay.

Roon Radio takes about the same amount of time to turn on.

Server uptime: 2 days, 17 hours

At 12:55 local time, I restarted the server, and Roon started working quickly again:
Tracks switch within 2-3 seconds.
Roon Radio starts within 3-5 seconds.

The homepage and artist information load almost instantly.

Hello @Atiss,

Thank you for the detailed timeline and for monitoring the behavior over those few days. The specific performance degradation you are describing—where the interface slows down, track skipping delays increase over time, and a quick server reboot temporarily restores snappy performance—is a known behavior that our team is actively tracking.

Our R&D team is currently working on improvements in this exact area, specifically focused on stabilizing memory consumption to prevent these long-term server slowdowns.

While we do not have an exact release date for these specific changes just yet, they are expected to be included in our upcoming updates. Please keep an eye on the official Roon Software Discussion > Software Release Notes section of the Community site.

Once the update addressing memory stabilization is released and installed on your Core, please let the server run normally. If you find that the performance still degrades after a couple of days, please let us know and update this thread so we can take a fresh look at your diagnostics.

Thank you for your patience while our team works on these improvements!

1 Like

Good evening!

Logbook update:
After yesterday’s 2.66 update, everything was working perfectly, as expected: fast response times, quick track switching, and quick loading of artwork and info.

Today, after one day and 30 minutes of server uptime, Roon slowed down again. Starting around 7:20 PM local time, there were long pauses (8-12 seconds) between track switching, increased loading times for the homepage, and slow loading of artist info.
Around 7:35 PM, the server was rebooted and is working as expected again.

Hi @Atiss,

As @vadim has mentioned above, our R&D team is currently working on improvements in this exact area, specifically focused on stabilizing memory consumption to prevent these long-term server slowdowns.

We don’t have any next steps in troubleshooting to offer, unfortunately, but it shouldn’t be long before these optimizations are fully rolled out in a future Roon update.

Until then, the best thing to do would be to reboot Roon Server when performance begins to slow down.

Thanks for your ongoing patience in the meantime! :folded_hands:

1 Like