What kind of performance/speed issue are you experiencing?
· The app takes a long time to respond to commands
Please try to reboot your Roon Server
· No, the issue is still the same even immediately after a reboot
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?
· Nucleus
Which model Nucleus do you have?
· Nucleus One
Timestamp of issue occurrences
· Been like this for a long time but most recently today
Describe the issue
Roon is slow to search, load playlists, change screens, and when a song is selected, it is slow to play the song. The only responsive and fast screens are the settings pages.
Roon Nucleus One hardwired via ethernet.
DNS set to 1.1.1.1 and static IP set for Roon Server.
Network is multiple Eero 6E all hardwired. No unwired endpoints
Endpoint is either Mcintosh DS200 or WIIM Ultra. Both Hardwired.
Describe your network setup
ATT Fiber Internet 1GB in bridge mode to EERO Pro Gateway which splits off to several EEro 6E endpoints. All are hard wired with Cat 6 ethernet cable.
Thanks for confirming your library size — with ~8,000 tracks, that is well within what a Nucleus One should handle comfortably, so this is not a scale issue.
Since you’ve already ruled out network hardware, DNS, and background analysis, and since reboots only help temporarily. At this point, the best next step is to reinstall the Nucleus operating system. This refreshes the OS and core services without touching your internal music storage.
You can follow the reinstall instructions here:
Once the reinstall is complete, let us know how the system behaves — whether the performance is restored or if the slowness returns. From there we can determine whether we’re dealing with an OS-level issue or something deeper in the database.
Unless there are unidentified albums/tracks, then a single core could be getting taxed due to repeated attempts of identifying them. Still happens sometimes.
Thank you everyone for your input. I Reinstalled the OS and everything seems to be working fine at the moment. I will update if anything changes before this topic is closed. Thank you!