ROON painfully slow after update with large library sizes [Roon Investigating]

Roon Core Machine

Windows 10 Pro

11th Gen Intel(R) Core™ i9-11900K @ 3.50GHz 3.50 GHz
128gb ram

Networking Gear & Setup Details

Netgear Nighthawk AX6

Connected Audio Devices

Sotm SMS 200 ultra

Number of Tracks in Library

500,000 plus

Description of Issue

Since updating to Roon Server Version 2.0 build just before 1223 my Roon slowed down tremendously. It sometimes takes 5 minutes for music to start playing. I have rebooted several times and it says it is adding and indentifying 10,000 tracks, but only about 14 are added. I have not added any music.

No change after update. Does anyone have advice on what to try next?

I have similar behaviour on my iMac with i9 8core, too. 30 to 40 albums adding takes minimum over night. And all the time when starting and nothing has changed in my library RoonServer has some thousands of tracks to check in the queue where later nothing is added.
885.000 tracks, database is 87 Gb.
This must be a bug. This all started when an update came in the midth of february where Roon worked on the internal database.

I agree. It is probably a bug, I am hoping they fix it soon. Roon is unusable as is.

I am using NUC12 as Rock server. Similar problem. Roon is not useable for me more than a month now.

Hi @sandmanct, @Bernd_Ruths1,

Thank you for the reports and I’m sorry to hear you’re experiencing slowness. The tech support team will be pulling automated diagnostics from your Cores to help expedite our investigation - please leave your Core online for several hours at some point in the next few days, so the report has a chance to reach our server.

In the meantime, to clear up the possibility of erroneous audio analysis, can you please share a screenshot of your Library clean up settings window? Navigate to Roon → Settings → Library and click on the “Clean up Library” button. This will open a dialogue box listing tracks that are seen by Roon but not added to the library. Are there are a significant number of track files available to clean?

Additionally, it’s worth refreshing your Roon database (after creating a reliable Backup) to stabilize conditions:

  • Create a Backup of your current database
  • Exit out of Roon
  • Navigate to your Roon Database Location
  • Find the folder that says “Roon” or “RoonServer,” depending on which you’ve installed
  • Rename the “Roon” folder to “Roon_old” OR the “RoonServer” folder to “RoonServer_old”
  • Reinstall the Roon App from our Downloads Page to generate a new Roon folder
  • Verify if the issue persists on a fresh database before restoring the Backup

The tech support team will keep a close eye out for your responses.

Hello Connor,
thank you you registrated our problems.
First of all, my RoonServer is running from now on for about 9 hours, so you can have a look at it.
Second, here is the screenshot of the Clean up dialogue. It shows 350 tracks, that could be cleared. Some 2 or 3 weeks ago I cleared the library of maybe 2000 tracks with this dialogue.

Does refreshing my Roon database after backing up mean to completely read in all of my 885.000 tracks?
Besides that this will take much much time, I had then again (yes, I did this last year because of the problems with the missing native .net for Mac) to manually restore my playlists with thousands of tracks and the bookmarks, too, right?
This would really be insane… I don‘t want to think about that.

Hi @Bernd_Ruths1,

Of course. No need to take the database refresh step if the specter of re-analyzing tracks is too grim. It’s a more procedural step than a surgical fix here.

Do you have any playback delays as reported by the OP, or are your symptoms limited to importing and analyzing tracks? Are slow import times limited to large filetypes, or do you experience this with low-quality tracks, as well?

The team is actively investigating diagnostics and will have a more precise step shortly once we sync with QA. In the meantime, an initial parse of recent diagnostics does indicate your storage location is failing to mount properly, possibly causing IO errors and delays in loading locally stored files through backend or temporary filepaths.

@sandmanct, we’re also investigating diagnostics from your account and will follow up shortly.

Yes, there are always playback delays on really all kind of files. Delay is longer when Roon is painfully slowly adding new albums and I think a bit longer with large filetypes, too. A typical short delay when no background activity is happening is about 15 to 40 seconds. With activity in the background, that means adding new tracks this can take several minutes before starting to play. Mostly, the track with the acoustical graph at the bottom shows up in some seconds but playing only starts like said before. Longer RoonServer runtime often means longer delays.
I tested this with Roon instead of RoonServer on the same iMac. Same behaviour there, just a little bit quicker. It doesn‘t matter which Roon endpoint I use - La Rosita Gamma, the iMac itself or my 2021 iPad Pro - there‘s always a delay like said before.
My latest imports of 238 tracks took 9 hours and still left something to add. After reading in new files, there are typically 2000-3500 additions showing up in Roons activity window, but in the end only adding 500-1000 tracks. This are exactly the new album tracks I sorted in the folders. What are the other additions showing up in Roons activity window?
Maybe I should mention that the whole library resides on 2 volumes:
One is an iMac internal 7.7 TB NVME SSD with 5,65 TB of music. This is an APFS volume. The other is an external 64 TB Thunderbolt raid with 42 TB of music, this is an HFS+ volume. The 64 TB raid is for sanity purposes regularly checked with DiskWarrior.
I will later post a picture that shows the scheme how I store my data. Most album folders contain graphics more or less, often embedded artwork and much in hires. There‘s mostly a music analysis graph for every single track present, too.
Since the Roon 2.0 update in October with the .net version for Mac until 2.0.10 everything really worked flawlessly, no bugs for me.
Backup is done on a similar 80 TB raid.
Why there are i/o errors on the mentioned volume is a miracle to me. How could the storage location fail to mount properly?
What would you say when I did a backup of the Roon database (which I backup regularly by drag and drop of the RoonServer folder, I have older databases back to 1.8), then route Roon to the backup raid, the 80 TB volume?
See my system maxed out in times of storage size, storage speed and RAM. To solve the actual problems here will for sure help you gaining experience with large libraries for the future.
My RoonServer will be on for the next 13 hours, so you can again have a look at it.

Here is a screenshot of the folder structure:

Compilations, classic albums, audiophile and other collections are stored in the same “Music” folder:

Hi @Bernd_Ruths1,

The team is actively investigating this issue. As you’ve suspected, it appears to be limited to users with large library sizes (roughly 700k tracks and above),.

Doubtless, this is true. I appreciate your efforts to assist in pinning this one down. I’ll report back shortly as soon as the team has a more precise sense of: 1) what’s wrong and 2) a temporary workaround or permanent fix to restore your system.

Ok. I’ll wait for the fix. I cleaned up my library and it maybe helped a little. Still long delays.