This is likely masking Roons problems. Whilst I don’t get really any performance issues and no dramatic slow downs other than search server side issues, when core is rebooted it is snappier than it was prior to doing so. If you happen to be doing some editing such as grouping or tagging a lot of albums going back and forth to album back to albums page select repeat. Over time this really starts to impact and it does get sluggish. I’ve noticed this happen quite a bit. Regular use doesn’t have this affect.
4 Likes
Would not see NAS or core on NAS as a common aspect of performance problems. You have to know the specs of your NAS and connect as well as use it properly. In this case roon can run as smoothly as on a NUC or whatever with a big library and DSP and everything you want. Having core and storage and backup hardware under one roof is reducing complexity. I wish there would be a 16 or 32TB Nucleus by roon offering the same level of redundancy and backup capabilities as my NAS. Would switch immediately even being willing to pay 5 grand for the Titan.
I know more people running Nucleus having problems than people running roon on a NAS with issues. NAS users tend to have a certain interest in monitoring performance of their machine and you have the tools for that on board. Nucleus´ users tend to take it as a ´plug and play forever´ solution which it was advertised as.
Probably what the majority of roon users is intuitively doing right without being aware. It’s comparable to people treating their (ICE) car intuitively right by never taking it onto a racetrack or flooring it while the engine is cold. But some people do, and I hope roon will offer a better solution for them as well.
We should not forget that some potential factors of performance problems such as unreactive internet connection or albums with lots of references are not really in the power of the user to oversee and change.
1 Like
My Roon (Windows 11) is still slow and I’ve just tried the ‘The The’ search and yep! it crashed! Meaning the Windows Roon Remote crashed and when I try to restart it, the server (Innuos Zenith) is not found, so I have to physically restart the server.
I haven’t tried the dreaded ‘The The’ search for a few weeks in trepidation this would happen & the slowness issues are still there.
It’s our propensity for thunderstorms, one brewing as we “speak” and my paranoia for losing kit that causes restarts . Add to that almost daily power cuts by our power utility
In a different situation I may leave on 24/7 but it does indicate that this restart regime does help Roon no matter what the reason 
1 Like
I restart Room whenever it is performing badly and it mostly fixes things (usually weekly these days). I am pretty sure your at least daily restart process keeps your Roon system running in it’s best possible way.
One thing that I just changed that seemed to make a massive difference is the DNS. Obviously everyone knows this advice but what I didn’t expect is that just setting it on my router was not enough.
What I was seeing is slow times for opening albums, a delay when loading my library and adding albums to my library took a silly amount of time. This was with my DNS on my router set to Google and backup as cloud flare.
I then changed my ROCK settings giving it a fixed IP and setting the DNS on it to Google. All of those problems immediately disappeared.
I have no idea why this had any effect at all, I would of expected setting it on my router would have the same effect as on device.
It’s does unless you override it on local machine with something else’s. Setting on the router sets dns for entire network to use the server you set. Setting it on the device in question I found can cause issues if you loose internet as now it will be trying to connect directly and not to the router and has issues with local network ops. Not that this matters as Roon won’t work without internet but if you did this on another app that works without internet I found it affected the device from operating without internet.
But in the case of Roon, it did not have the same affect.
Set on my router, performance of Roon is poor.
Set on my NUC, performance of Roon is good.
Makes absolutely no sense to me 
There should be absolutely nothing one has to do “right” with such a product except following the recommendations for the hardware and networking environment.
It is supposed to work within the limits defined by the vendor. Roons definition does not even mention “unidentified tracks”.
3 Likes
Anecdotally, it appears that NAS users actually have fewer problems once they get going. Count me among them.
1 Like
Sounds like the router side it wasn’t set correctly then as it works fine for me on the router. I trailed a private dns service for a while to Adblock and it tells me what my router is actually using currently it says Cloudflare.
It was definitely set correctly on the router 
I think the two of you are talking about different things.
I think @crowlem initially set the forwarding address on his router to a faster provider not set DHCP to bypass the router.
I am assuming he then bypassed his router.
Routers are often a bottleneck and ISP’s like to set them to forward all traffic to them to help monetize our information.
Best performance for Room seems to be bypassing internal DNS server’s completely. I even found that my Synology DNS server was rate limiting Room as it made so many requests
1 Like
@Michael_Harris thank you for explaining it better than me this is exactly what happened.
1 Like
Not what I am on about at all.
I think that is a common scenario, and for most people it makes total sense just to set the router to forward to the preferred server.
Routers tend to be way underpowered and are not expecting Roon levels of DNS traffic. Many were also designed to manage 20Mb of traffic and not the 250Mb to 1Gb that is common now
Bypassing the router as you have done has given you your boost in Roon performance and hopefully more people will pick up on that
1 Like
Ha ha well one of you was 
DNS should go to the router or an internal dns server these are both configured to point to a specific dns server of your choice. I made ann error once and wondered why nothing would talk to each other with no intertent on my wireless network. All the aps I had configured to point to googles dns not the router so when no internet they all through a wobble and would not work properly. When I put it back to be the router all internal stuff worked then as it should without any internet connected.
I guess if the router is subpar then too many dns requests may overwhelm it but modern stuff should be able to deal with this. A lot of devices don’t allow separate dns and dhcp settings has to be all auto or all manual as is the case with rock so this means could lead to other issues as we all know setting up a fixed ip on the device is not the right way to go.
1 Like
I do that to my own internal servers for everything besides Roon, which works better for me going directly outside to Cloudflare.
For those of us who buy decent third party routers I doubt there is a major issue here.
Many ISP provided routers cannot handle the kind of DNS traffic that Roon seems to generate.
My router is a Netgear Nighthawk, I don’t think it’s a subpar router, maybe the level of requests from Roon are just ridiculously unreasonable?
1 Like