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

Three days ago, another user posted on your ‘feature request’ thread the following:

I tend to agree… There certainly are problems rooted in design decisions taken more than ten years ago… There probably is no easy solution to the performance problems, when server processes like metadata updates or storage library updates drive one CPU core to 100%…

I am convinced Roon staff do see this, but they don’t wish to go into details and place their cards on the table, for not seeing an easy way out of the problem…

Or maybe they have long since begun work on a redesign and reimplementation, and someday we will be surprised by a much better Roon… If and when that’s the case, I will be evaluating Roon again and consider to switch back…