This doesn’t sound like a core performance problem to me at all. Or to be precise, it might be something related to the Roon software on your core, but I doubt it’s a hardware performance problem.
I don’t think that’s an issue either. The performance for reading audio files is easily sufficient for any reasonable HDD (even spinning), and the HD is not involved in Roon interactions like searching
Are you speaking about the LAN connection or an internet speed test? 1-200 mbps would be very poor for a LAN, where 1 gigabit speed on wired ethernet should be the norm nowadays.
For the internet connection, however, 1-200 mbps is easily fine. All that happens there with Roon is the fetching of audio files, which are like 5-10 mbps.
This is different, though. There is a lot of buffering with Netflix, so intermittent bandwidth changes are not a big issue. There’s also no complicated UI and database interactions going back and forth from remote to Core, like there are with Roon.
Generally, searching and other Roon UI interaction speed (other than playing) is not typically bandwidth-limited, and the whole thing doesn’t seem like an issue of continued throughput (i.e., bandwidth) to me, but more like an issue of responsiveness / latency. How are your ping times?
- From a PC on the LAN to the Roon core
- From a PC to the central router?
- From a PC to an internet host like Google?
https://www.howtogeek.com/355664/how-to-use-ping-to-test-your-network/
Normally I’d suggest trying to change the DNS server on the router to a fast one like Cloudflare, but as the router is central, I suppose you don’t have the option. My gut feeling, however, is that the central router or something else on that network may be the most likely culprit.