@support I have noticed with the newer builds that RoonServer maxes out a single core of my pc during its metadata updates. This is at random times when I am wanting to play music and during this time all remotes loose connection and music stops temporarily. If I ssh into my machine which is running latest version of DietPi (Debian) and Linux version of RoonServer and run HTOP I instantly see one of Roons processes Roonappliance is through the roof. It’s at 150+% and sticks at this level for about a minute then drops to between 70/80% for the rest of the update, with this drop it then resumes connectivity. Using Tail on RoonServer logs during the high level of cpu activity I can see Roon was performing metadata updates and nothing else.
I have to ask why would this process max out a cpu core so much my library isnt huge, doesnt have lots of unidentified albums and is all local music. I Subscribe to Qobuz but have no favourites. I did sub to TIdal but cancelled this recently. I do notice Tidal comes up in the metadata updates and says I am on MAX which I currently am not.
My machine is no slouch, it’s an 11i7 11390H, 16gb ram. M2 drive for db, music on ssd. Its base is 3.4ghz with turbo up to 5gz. No other cores are maxed out and all other services on machine are not affected it does have 4 cores, 8 with hyperthreading. I know Roon is a single core process for these activities so something seems to causing it to run amok.
Spoken to @Andreas_Philipp1 and he has noticed the same issue and reported it before.
As we can’t scheduled updates, this is happening during normal listening and isn’t making my return to Roon very enjoyable.
Roon does metadata trawls itself to update metadata at regular intervals not just on adding music. Its always done this and is been discussed many many times. Its how it updates material when added to its sources such as MusicBrianz and Tivo. The library also has a rescan interval which it will perform as well. When this happens seems to be random.
I haven’t seen any official documentation on the metadata trawls though. Maybe i’ve just missed this…
Anyways, i do not see any spikes in processing, at least what i am aware of.
I do have mostly local files thpugh, and some 3-400 albums favorited on Qobuz. (No TIDAL)
Could it be your choice to keep the service accounts without active subs causing this?
I dont have this. I have one Active Qobuz account tied to Roon nothing else, I just dont keep favourites. I have ab out 33k tracks of my own in my library.
I think (might be wrong) you used to keep the Tidal Service account to get “the weeks releases” etc. But not having an active sub didn’t allow streaming of anything.
If i am mixing you up with somebody else, i apologize!
And my second question is, have you “cleaned your library”?
Or might there be favorites still associated with. Tidal such as in playlists, favorites.
I maintain my library all the time. I appreciate you trying to help, but this is up to Roon support to answer why Roons metadata updates would thrash a cpu so much to bring Roon to halt for all other of its processss. To me it feels like something’s off with this side of things. Roon barely registers at all during normal operations even using DSP convolution at 192/24 it doesn’t show any processing speed and all other aspects are lightning quick. DiskIo is optimal to as in checked using the provided OS tools. I don’t have local playlists with Tidal content and they would not be active without the account active in Roon anyway. I have now deleted my Roon cache but I really should not have to resort to these measures if an account has been removed from Roon.
The team is eager to investigate, but we’ll need a timestamp (or at least the last date you observed this event) to confirm our findings.
Logs additionally show RoonServer churning through duplicate tags. Among these 32k local tracks, how many have tags applied? Do you have any tags applied across all these tracks?
Hi @connor roughly around the time it started the metadata update which was 11:07:40 ish pm on the 14th July. I had just started to play an album by Cassandra Jenkins and as soon as I did moments later Roon lost connection to the core and then music stopped a bit later. I could ssh in so network not a problem only Roon affected.
I do not have tags on all music a few thousand maybe to identify the place they come from. I also don’t have many with more than one tag to my knowledge. I do see that Roon still seems to think I have tags for ones I removed from the system, such as Bandcamp which shows up twice in the logs. I had a ticket about issues with this tag aa Roon stopped recognising it when added as an RoonAlbumTag. Support could not answer me as to why and I sent them a copy of my DB.
Please see my response on the thread you linked - it’s very likely a known, esoteric bug.
As for this thread, development has provided additional technical context:
All library management in Roon is performed on a single operating system thread. This was an architectural decision to protect database integrity, a sacrifice in processing for corruption resilience. In its current product form, this single-core library management immovable reality of Roon’s implementation. As a result, Roon can’t use more than one core to perform library updates, including metadata syncs with upstream servers.
This doesn’t mean you’re encountering normal behavior and can expect poor performance or freezes as your reality. We have ticketed work to improve tagging and there’s every reason to suspect tagging is exacerbating or even causing this condition. If symptoms are worse than when you last submitted a copy of your RoonServer folder to our QA team, you can provide a current copy here to expedite their investigation.
Thanks for the response Connor. It does seem odd that it completely fell over I would perhaps expect it to be slow during a full library analysis but this morning I performed a complete library re-identify and it did not have this issue even though cpu was still maxed out. A little laggy but not loosing connection. I assume this process would be similar to when it does the deep analysis of the metadatasvc process or am I incorrect here? If it is tags then this bodes the question why allow tags if they have such an impact on database updates. I look forward for some updates to improve performance here.
I am currently re-analysing all my media when done will upload a new db for you. I did post another db issue today which I feel perhaps is related to these issue?
I added a new album about 30mins ago and for no reason I can fathom Roon decides to go in to a full metadata update mode rendering it useless for a while and maxing out the one core as I have shown before.
Here is htop its been at 150+ during this process and its still going over 35 mins later.
