Server unresponsive during metadata updates due to maxed-out single core (ref#UA2SW4)

As discussed in a PM this topic has been returned to Feedback Roon’s product team will see it here (they may not comment but it will be read), Roon’s support team have already taken a steer from Roon’s product team, that why it was move to Feedback in the first instance. Support have little influence on product design changes.

Different beasts but the same result, they allow you to select and play music, that sounds the same if DSP is not used.

I use them interchangeably and enjoy both, there are features in Roon I really like and there are features in LMS that I like. Overall LMS is an amazing “free” solution that in and of itself was worth moving from Rock to DietPi for, the fact that it takes almost 0 processing overhead is a bonus.
Not sure if I count LMS being written in Perl as a bonus or not :rofl:

That was done. Or am I missing something here?

Those were querying the reason a post was deleted. Since that is reinstated, they add nothing to the discussion. I’m not sure what point you are trying to make, but the only reason your post was deleted in the first place was that you moved the thread out of a Feedback discussion.

If you intend to reply, let’s do that in a PM.

8 months actually as July last year when I returned after a two month hiatus due to the broken remote app issue.

I will say it again my library isn’t large in the scheme of things 35k tracks. It’s mainly flac with some
Lossy. I don’t have huge amounts of subfolders for it to deal with just artist/album. Classical has its own folder as film soundtracks then artist/albums. I dont have a lot of unidentified albums 9 at last count. I add ones that aren’t to MusicBrainz. These where left as are obscure classical which I have no desire to fix.

Not much I can do really. No other app has an issue with it. Roon doesn’t want to fix it so I am left with two choices. Keep using and and suffering when it decide to happen, or move on. I decided the latter as I pay yearly and I am not paying for software that doesn’t work as it should. It’s definitely some change they made and it’s had a detrimental affect on performance for some of us. Combined with many other bugs that get left and added with each new release. It’s just a bit much to keep paying. It was a good ride but time to get off. I’ve sent enough kit back that doesn’t meet my requirements so this is no difference. What I have moved to isn’t perfect but it’s basics are solid, it keeps growing and developing being open source and free it has many developers all working on their own bits. They are helpful and open generally and you get to see what’s on the roadmap and what certainly won’t be.

You slacker you :wink:

All -

See this thread…this poster did some investigating and I wonder if we can leverage this information?

Interesting that we see more and more similar reports yet Roon support doesn’t draw any connections to this “known” (at least observed) issue.

So, I know that I have seen slowdowns on AMD machines on windows with Roon server, and the above poster saw CPU core usage skyrocket on an Intel CPU on Mac.

Here is the question, because I am not sure I have seen this: has anyone seen a CPU usage spike on an AMD chip on Linux?

I’m not getting my hope up, but maybe that is the magic recipe?

The problem is still Roons to fix. It’s their software that and only their software that has this problem. Changing perfectly good hardware to bypass it isn’t a solution, and not one I will be looking at trying. Several weeks now without Roon and all is good.

I am running on Intel 10th Gen i5, so can’t add anything to that sorry

I have to point out that the culprit in the spikes I am observing is a specific system process, the infamous “kernel_task”. The spikes are not necessarily related to Roon; when either the server or the client are off, the spikes continue haphazardly. What is curious is that when I terminate processes related to contacts, calendar and so on, kernel_task calms down and drops in the hierarchy of resource intensive processes.

By no means am I an expert on these matter, but simple observation tells me that my MacBook has reached the end of its lifespan. I am not a conspiracy theorist, but it is interesting that the gossip in town is that at least intel chip Mac’s have a lifespan of 5 years, after which it, well, let’s say it’s useless - not my words and I believe Apple would agree with this diagnosis.

Cheers!

Christan for most of us we are able to see RoonApplience peaking at around or above 100% when this slowdown happens so that suggests it is Roon.
Also confirmation from Roon Staff that it is doing what is expected helps support that, it is part of the way the system was designed (or not depending on how you look at it)

Thanks, Michael.

I guess my Mac is worse off than I thought. If, on top of the way Roon has been programmed. I am getting drastic increases in CPU usage without Roon, I am stuck.

Thanks for the clarification.
C

No problem Christian this is a long running thread, with limited feedback from Roon staff until recently.
A couple of the respondents have now left the Roon ecosystem for LMS, because of this issue.

Hopefully you can get the issue down to being intermittent and reduce the frequency until Roon deem it worthy of some development effort