After running smoothly for quite a while roon keeps failing me for two weeks now.
roon keeps cpu usage aound 20 percent most of the time. Not sure what is going on.
cpu usage every once in a while goes up above 90 percent, thereby killing any stream.
Clients see messages like qobuz loading slowly or something related to the roon core.
Sometimes the stream continues, sometimes it does not.
No dsp except what is needed for volume control.
Not client related
restarting roon and/or system did help early on but does not help anymore.
Had this before, but not as bad. Switched to a machine dedicated to roon because of this issue.
Is there a way to see what roon is waisting its (and my time) with and to stop this madness?
Restarting the server does indeed help for a day or two. A (built in) way to automate this or initiate a restart from the client would be a desperate measure, but it might be helpful. But this is complicated because roon needs a user to login before it starts…
Thank you for that link, @Rugby. Observations from browsing the logs:
Logs show numerous “Warn: bad track/media “CD”…” entries. Just checked one of these. It displays and plays just fine. No explanation for this to be found anywhere.
Roon seems to be going through my collection over and over again without any particular reason. (1)
As the collection is pretty large this generates constant and heavy load.
I suspect roon delays this action for a given time after startup - maybe 24 to 48 hours, because everything is just fine before it is not.
Not sure if roon keeps track of what is done and what is not during this process. Given my large collection restarts may be counter productive while also necessary to use the product at all. Sort of Catch22.
I would love to see a way to control this, like make it happen when nothing is streamed and stop it when I listen to music, for example.
As things are right now it completely ruins the listening experience.
(1) Really lots of these entries. Maybe these kill performance, if there are too many…
05/17 19:33:10 Trace: [dbperf] flush 848857 bytes, 308 ops in 47 ms (cumulative 1531588471 bytes, 724116 ops in 328519 ms)
05/17 19:33:10 Trace: [library] finished with 474 dirty tracks 37 dirty albums 242 dirty performers 261 dirty works 306 dirty performances 81 dirty genres 62 clumping tracks, 0 clumping auxfiles 45 compute tracks, 0 deleted tracks, 78 tracks to (re)load, 0 tracks to retain, 0 auxfiles to (re)load, 0 auxfiles to retain, and 1120 changed objects
05/17 19:33:10 Trace: [music/searchindex] [search-index] removed in 0ms: 34 albums, 193 tracks, 20 works, 24 performers, 0 labels, 25 genres
05/17 19:33:10 Trace: [music/searchindex] [search-index] added in 10ms: 34 albums, 193 tracks, 20 works, 24 performers, 0 labels, 25 genres
05/17 19:33:10 Trace: [dbperf] flush 0 bytes, 0 ops in 1 ms (cumulative 1531588471 bytes, 724116 ops in 328520 ms)
05/17 19:33:10 Trace: [library] endmutation in 393ms
Some NAS models exhibit poor performance when compared to USB or internal drives, particularly WD MyCloud and Drobo products
There have long been issues with the watching Roon does keeping NAS drives awake.
I would highly suggest having the library on local drives. I personally use internal drives on my servers. My NAS holds a copy.
“Warn: bad track/media “CD” - “Just checked one of these. It displays and plays just fine.”
What do you mean by “Just checked one”. Did you play it in Roon? Did you play it using a different media player?
You might also want to look at Settings/Library and check Skipped Files and see if anything is being reported there. It could be that there are several files which are not importing for some reason and Roon is continuously trying to import them.
myCloud: Thank you for pointing at this. I did extensive testing before switching from local to NAS. I would think that they cause trouble all the time, if they are the root of the problem.
roon and roon database are on a local NVMe ssd with plenty of space.
“Warn: bad track/media “CD”: listened to the whole album (great rediscovery, by the way). All tracks played just fine.
Skipped Files: Their count is 36. No change since I last checked them two months ago.
I should mention that the system is running nicely since I restarted today (23/05/18, 11 am), roon taking less than .5 percent of cpu most of the time. There are peaks up to 30 percent, but no constant high load.
24 hours later roon starts misbehaving again. Just wanted to listen to todays new arrivals it stops playing for no reason at all.
Task manager shows about 20 percent cpu load for roon, plus healthy traffic on network and internal disc (see screenshot). Please, what is going on there?
Restarting roon in the way described helps a great deal. I am somewhat frustrated that @support does not react at all. I am with roon since day way one and am used to that, but still…
Not sure if the cases have anything to do with each other, but I used to notice similar behavior of my previous Roon system eating up RAM without limits and kind of forgetting to befree it afterwards. 74% RAM usage could be already on the brink of what is causing the system to look for alternative storage and therefore slowing things down significantly. Funny thing was this was as a consequence driving CPU usage to similar levels you are experiencing slowing Roon down even more.
Doubling the amount of RAM was the cure in my case. Not sure if this is possible or anyhow a solution in this case as you are having a lot of RAM already. But 20% usage in idle already having a quite powerful CPU seems to indicate a deeper problem in my opinion.
Thanks you for your comment. I agree there must be something else going on, though I am lost at what it might be.
I even tried 64GB of memory, but as it turned out this was never a limiting factor.
Also, the “system” itself does not use up resources in any meaningful way. It is just roon (and no other app) going bananas and generating breathtaking cpu loads after a given time.
Automatic restart is a workaround, not a solution. Roon does not seem to care, unfortunately. Nobody asked for logfiles. I am sure that an insider having a brief look would isolate the problem in minutes.
Okay, we can rule out the lack of sheer computing power. But something within Roon seems to keep the system overly busy. 22% of CPU usage and 19GB of RAM in idle does not seem normal to me. Having a significantly slower CPU in my system and also a >100k library if I enable all folders, my system uses much much less computing power when Roon is in idle.
The second thing I checked when I was experiencing similar behavior with my previous, outdated system: deactivating storage folders one by one and thereby identifying if something in the folder or file structure or database interdependencies is causing Roon to go crazy. Two folders (out of 20) turned out to be driving Roon to despair (in my case it was 1 folder with operas and 1 with classical editions).
Ben with the support team here, it’s great to see you on the community again! You have my apologies for the long delay in getting to your thread. We were able to review core diagnostics, and are seeing a fair amount of bandwidth being used on scanning and indexing your local library.
We need to review these errors with our development team next week, but in the meantime, I’d be curious to see how things run if you temporarily disable your local library and only stream audio from Qobuz. I understand this is inconvenient, especially going into the weekend, but this would be a good item to test in the meantime.
Another option to test over the weekend would be to refresh your database. Steps to follow below:
thank you for loooking into this. I just disabled local storage (two locations) and the daily restart of roon server. I will check how things are going on monday latest, but maybe I will listen to some music tomorrow afternoon. Guess everything will be ok without the local library.
Part two (“database refresh”) is not really practical, as lots of music involved and it takes quite a while. Will do it if there is no other way but pass on this right now.
So I am running qobuz only now, 26253 tracks, 2169 albums. CPU for roon appliance is > 4% most of the time, peaking to 20%. There is also constant network load between 5 and 21 MBit/s. Not sure if this is cleanup after taking way local files.
Had one occasion of “qobuz loading slowly…” right at the start of my listening session today. As I write this, I got “waiting for your roon core”, before music stopped playing.
Now, with nothing special going on, roon appliance eats up 5 to 10 Ppercent CPU before peaking above 50 percent. Screenshots show that condition (not the peak, unfortunately).
Again, this is without any local files. I go back to a daily rebooting schedule an full library, as this sort of works to listen to music. Look forward hearing from you.
