Post-update performance issues with ROON Nucleus Titan and large library (ref#5NRO4F)

Support Nucleus Support
1

Select your Nucleus model from the list below

· Nucleus Titan

I'm having trouble with my Nucleus hardware

· Other

Select the option that fits best

· The Nucleus boots up and I can connect to it in the Roon app without issue, but I have a question about configuration/storage/attached devices

Describe the issue

My current status of ROON Nucleus Titan: using it as server with 8TB internal SSD storage (used 7.3 TB) + connected an USB 8 TB SSD external SanDisk hard disk via USB too!!
Total content on my ROON server now: 7'875 artists, 31'763 albums, 408'843 tracks + 203 composers!!
Everything worked very well for the last few days before last update!!!!!!
Don't tell me I would have too many data!!!!!!! As I've said: Everything worked very well before too!!!!!
It's true that earlier there were some corrupt files included too!!! But in the meantime I've deleted them all!!!!
There are just some cover pics left which have still to be corrected too!!

I'm really not happy with ROON's software the more as Nucleus Titan could read + play all my music too!!!
Everything is very unstable too!!!!!
And corrupt files, bad covers or other mistakes too should never be a reason for a system crash too as you've earlier stated once!!!!!!!!!
A sophisticated + modern system should be able to skip them all, inform the clients about eventually mistakes or bad or false music quality too + just show or use the good quality music data with the indeed beautiful ROON software too instead of just crashing!!!!!!!!!!!!!! + get customers "angry" too!!!!
Should my data volume really be too big I would really pay more to show it with ROON too... another option or opportunity for you too!!!!!!!
So don't tell me I've got too many data!!!!!!! Otherwise I've to look for an other opportunity too + I would give up the beautiful ROON possibilities too! Size can never be an issue too!!!!
Kind regards, thank you very much for your understanding + have a good weekend too!
Hanspeter Dettwiler from Switzerland

3

Hello @Hanspeter_Dettwiler

Thank you for the support request. We were able to collect the logs from your Titan, and they gave us a much clearer picture of what’s happening.

First, a few things from the earlier troubleshooting are now clear: the corrupt files are gone, the cover art cleanup is nearly finished, and your internal storage is at about 80%. So none of those are what we’re looking at now.

Your library has also grown since the last logs, from about 376,000 to 409,000 tracks - I have to say, the speed at which this collection is growing is pretty impressive :slightly_smiling_face:

The important part is that the latest update did not cause the instability. Before build 1683 was installed, your Titan was already crashing dozens of times a day because it was running out of memory while trying to process the library.

Build 1683 actually improved things quite a bit. After the update, your Titan managed to run for 29 hours without a single crash.

What is happening now is that Roon is trying to catch up on metadata updates.

Normally this happens gradually in the background. Because the Titan had been crashing so often, that work kept getting interrupted and never finished. It is now trying to work through almost the entire library in one pass - about 393,000 tracks.

That is a much heavier workload than normal, uses considerably more memory, and also explains why Roon feels so slow while this is happening.

Your latest logs show that the Titan had been running for almost two hours and was already about 60% through the job, fingers crossed this run will get to completion.

So for now, my advice is simple: leave the Titan alone for a couple of hours. Don’t restart it, and ideally avoid using Roon heavily until this finishes. Restarting would interrupt the work again.

If it completes, my hope is that things will become stable again and noticeably less slow, since Roon can go back to processing a much smaller amount of metadata each day and will need less RAM to do it.

That being said, with a library of this size you are right at the edge. Long term, there are really two options: rebuild with a smaller library, or increase the amount of RAM.

Whichever route you choose, Support can help you through it.

Cheers, Vova

4

Hello @Hanspeter_Dettwiler

Following up on the metadata catch-up job we described on Saturday. It should have had time to finish by now, so we would like to know where things stand.

Could you please tell us:

Has the Titan stayed running, or has it crashed or restarted again since?

Does Roon still feel slow, or has the responsiveness improved?

Have you restarted it at any point, or has it been left to work through the job undisturbed?