Roon has never really recommended anything but music storage be local to the core. In fact, if you go back to those posts in 2017, Roon devs were pretty direct about keeping your music local and only using the NAS as a backup copy of your music files.
1 Like
Ah, my bad. 2017 was way before I started with Roon…
1 Like
Also, I should add that I’ve now moved back from running on my 918+ to running ROCK on an i5 NUC. The performance was “fine” but search results were slow, and in particular predictive search (the suggested answers that appear below the search box before you hit ENTER) were stuttering and filling in in a way that was visibly distracting. All smooth and peppy on the NUC again.
It was a good experiment, served me well, but happy to be back on a proper dedicated reasonably powered NUC. The 918+ turned out to be underpowered (as many have suggested) and I’m not going to upgrade a NAS to get processing power. It’s a consumer file device that does some other things well… but not this type of workload with lots of data dependency and need for low latency. Someone more technically competent than I can opine on why exactly. But I’m glad I went back to a “real” (dedicated) core machine.
Well the flexibility running a NAS solution are obvious - and you currently also mentioned to look out for that.
So in general there are a few things to consider or have in mind, but that very much depends on your requirement of the library. If you have a few hundred thousands songs in your library then things are high demanding. I don’t know why so many focus on a high performing CPU when even with lower consuming ones there is enough free room available.
I for example use a QNAP HS-453DX-8GB RAM which is completely fanless. It’s a 4 bay solution so you can have two M.2 SSD for the system and ROON dedicated to it for example and two SSDs for media files, fotos etc.
There is still enough power available to run DSP, convolution filters etc. also depending on your preferences.
2 Likes