RoonAppliance out of control

[Guy_Hussussian]

Hardware: Intel NUC 13
OS: Ubuntu 24.04.1 LTS
Roon version: 2.0 build 1470 - production
Music Library: 8649 Artists; 26172 Albums; 212569 Tracks, 179 Composers

My Roon Server is a bit out of control. Actually just the RoonAppliance process.

Pinned thread RoonAppliance
 CPU Min/Max/Mean:   100.9  145.2  115.7%
 MEM Min/Max/Mean:    43.8   43.8   43.8% 
Memory info: 6.65G rss 19.3G 
 Open: 71 threads

Memory keeps growing. Pegged CPU. RoonServer_log.txt shows a lot of this:

10/28 13:43:14 Trace: [metadatasvc] GOT [5133] (3790ms) Sooloos.Msg.Metadata.GetMetadataResponse:
10/28 13:43:14 Trace: [music/folderimages] set best folderimage for LibraryAlbum[1329455, Pearl Jam - Ten] to 56502
10/28 13:43:14 Trace: [library] finished with 11 dirty tracks 1 dirty albums 6 dirty performers 11 dirty works 11 dirty performances 5 dirty genres 1 dirty auxfiles 0 clumping tracks, 0 clumping auxfiles 0 compute tracks, 0 deleted tracks, 0 tracks to (re)load, 0 tracks to retain, 1 auxfiles to (re)load, 0 auxfiles to retain, and 34 changed objects
10/28 13:43:14 Debug: [query] Sooloos.Broker.Music.LibraryPerformer:6 dirty items, rebuild threshold: 2000, rebuilding? False
10/28 13:43:14 Info: [query] Sooloos.Broker.Music.LibraryPerformer: Process Removes/Adds (small) in 0ms
10/28 13:43:14 Debug: [query] Sooloos.Broker.Music.LibraryPerformer:6 dirty items, rebuild threshold: 2000, rebuilding? False
10/28 13:43:14 Info: [query] Sooloos.Broker.Music.LibraryPerformer: Process Removes/Adds (small) in 1ms
10/28 13:43:14 Debug: [query] Sooloos.Broker.Music.LibraryTrack:11 dirty (< rebuild threshold of 170055.2).  re-sorting item-by-item (internaltype=LibraryTrack)
10/28 13:43:14 Info: [query] Sooloos.Broker.Music.LibraryTrack: Process Removes/Adds (small) in 0ms

This repeats.

My music library is accessed over NFS share /mnt/nfs/multimedia/music/collection

So what is the difference between RoonAppliance and RoonServer process. Can someone point me in how to see RoonAppliance specific logs?

Thank you all in advance for your help.
-Guy

[noris]

Hello @Guy_Hussussian ,

Thanks for reaching out with your report. We’re currently looking into a similar issue, so I will add your report to the ticket tracking this behavior. It may take some time to get to the bottom of this issue, but please allow our devs some time to investigate this and we’ll get back to you once we have more details, or if you don’t hear from us please ping in a week or two to ask for a status update. Thanks!