What kind of performance/speed issue are you experiencing?
· The app takes a long time to respond to commands
Please try to reboot your Roon Server
· No, the issue is still the same even immediately after a reboot
Please try to reboot your networking gear (Router/Switches/etc.)
· No, the issue is still the same even after a reboot
Is there any change in behavior if you try to navigate to Roon Settings -> Library and set both Background and On-Demand Audio Analysis to Throttled or Off?
· No, the issue is still the same
Does the issue happen on multiple Roon Remotes (controllers) or just one?
· Issue happens on multiple remotes
Router Domain Name System (DNS) change
· I was able to change my router's DNS servers but it did not help
What is the operating system of your Roon Server host machine?
· Roon Optimized Core Kit (ROCK)
Timestamp of issue occurrences
· Not exactly, it starts in Summer…
Describe the issue
Search is extremly slow, the reaction time on Commands in all clients is up to 5 Seconds
I thougt the slow search depends on Tidal and changed to Qubuz. But there was no dependency.
Rock runs on an Intel NUC 11 Pro Board BNUC11TNBI70000 with 16GB and 2 internal SSDs, one for System, one for Music.
This runs very quick for a long time.
Thanks for reaching out. Can you please let us know the exact local time + date + search term you use, and approximatly how long it takes to recieve the result? You mention other commands also have this issue, can you please be a bit more specific? Does playback starting take a while? Are there delays when tracks transition from one to the other as well?
mh, whow. I tested it now and every reaction was very quick. On all Clients.
Can you tell me what you did? It was tough for months, almost unusable.
It was tough for months, almost unusable.
Thank you. Could I have solved this myself?
Glad to hear it’s working better! We haven’t made any changes on our end, as far as I’m aware. It was possibly an issue on the cloud or network side that resolved itself, but in any case happy to hear of the improvements.
I’ll go ahead and mark the thread for closure but should the issue return, please feel free to open a new thread with the above requested information, post a link to this thread and we can take another look, thanks!