Build 1525: Qobuz batch album removal from favourites [FIXED]

The machine I’m testing this on matches close enough a Necleus One with 8gb RAM (note: the RAM is important in this). I’m running Roon Server on DietPi.

I wish to update you on my findings.

I added 52 local albums and my Qobuz library consisting of 5595 albums. I turned off audio analysis. Total track count was close enough to 75k.

RAM use was 5.3gb. DietPi doesn’t consume a lot on this device. Let’s say 0.5gb. If this was a Nucleus One it would have crashed.

I decided to go all in and focus on all my Qobuz favourites. I selected them all and removed. Whilst it took a while to establish and asked if I was sure, I hit remove. After a while all albums disappeared from Roon, leaving my local 52 albums.

Pluoin checking My Qobuz app on my iPhone I slowly saw them disappear from the app. I checked with Soundiiz and they all but 19 were gone. Qobuz showed a remaining 22 albums.

I checked Roon’s library cleanup. Nothing was showing as needing to be cleaned up.

Ok, looks like a fix has been successfully.

A quick manual removal of the remaining albums. Both Qobuz and Soundiiz show zero favourites.

DietPi was showing Roon consuming 5.92gb of RAM, DietPi using 0.4gb. Thank goodness this has 8gb of RAM.

With all these albums gone, why was it sitting at nearly 6gb being used. CPU across four cores was less than 3.5%.

A reboot of Roon Server and RAM used by Roon is 628mb and DietPi 84mb.

As all the favourites have gone from my Qobuz app they will not reappear on Roon.

Well done Team Roon. Thanks :pray: :+1:

1 Like

An interesting observation, my sever has not yet gone above 4GB since it’s service was restarted as part of the update. It normally gets to about 7 or 8 GB after a couple of day’s and sits there untill it is restarted.

I would love for Roon to use more memory if it meant it was snappier in operation, but I guess you might only agree if you have additional memory above your current needs.