Roon Nucleus+, Samsung 860 SSD (2TB), files on Diskstation 2415+
Networking Gear & Setup Details
eero 7 or Plume → Ubiquiti Unifi USW-Lite-16; Nucleus, Diskstation and Mac are connected directly to that switch
Connected Audio Devices
2x naim uniti atom
1x PSAudio
1x Lumin U2 mini streamer
Various airplay, chromecast
Number of Tracks in Library
175K tracks
Description of Issue
Server extremely slow to boot to the point where anything can connect to it
Performance extremely slow doing pretty much anything; simple track playback not even obviously responsive to click until a while later, then starts playing
Extension list unreliable; only one extension (unfolded circle) appears infrequently making it impossible to use
Server can’t be contacted quite often; seems to crash a reboot (like just now)
Tried cleaning up database without any success. Tried lots of reboots, no change. Switched out network cables for brand new ones; no change. Switched from Plume 6e to eero 7; no change. Tried screaming and yelling at it; remarkably ineffective.
@benjamin - have I somehow left something out that is causing this to not be a support case? I don’t know how long I need to wait for a response, or whether this has been entered…?
Thanks for writing in and letting us know you’re having performance issues with your Nucleus. You haven’t left anything out - I appreciate your patience while our team works through each thread.
I notice that you have a large number of airplay and chromecast devices connected to your Nucleus. Does the same performance issue occur if you disable ~50% of these devices?
I’d also be curious to know the number of unidentified tracks within your current database. If you head to Roon Settings>Library>Clean up library (do not perform this, just review it) and share a screenshot, that would be helpful. It will look like this:
OK - I didn’t have a lot of CC/AP devices enabled (although there are a lot “present”). Probably six? I’ve disabled all of them. The only thing enabled now are the Roon Ready devices:
Thanks for the update. It’s likely here that the performance issues you’re facing deal with a current bug in our search index process - which we’re actively working on a solution for.
In the meantime, you could test out using a smaller subsection of your current library, which is less than ideal. Make sure to create a fresh backup before performing any edits.
I will follow up with more information as soon as possible.
Potentially, yes. As a next step, you could make a fresh backup, and test out fully removing your local library to see if your issue persists. You’d need to perform another library cleanup after disabling your watched folders.
Unfortunately, I don’t have any additional troubleshooting steps outside of that. We should have more information to share soon.
While this improved things a bit, there’s been a huge regression in 1359. My Nucleus works for a short period after reboot, then just stops responding. For example:
In the meantime, could you please reproduce a specific action that prompts a longer performance delay, and share the specific date and time, and if applicable, the track as well? From there, we can enable diagnostics on your Nucleus and take another look.
The weird thing is that it’s not scanning any folders: I have it set to not do that automatically. So it does it once, at startup. The crashing, etc, happens when it’s basically idle, doing nothing - the last one, as I said, happened at 3am or so…
Right now, it’s working OK, but it crashed 20 hours ago…