Slow Search Issues

Great stuff all works now.

1 Like

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.

Hi @support I am once again finding that Roons searches are slow .It’s taking on average 6-8 seconds to bring up results. I just did a search for The Beatles which I imagine is a popular search and via Roon this took around 7 secs this seems quite excessive compared to Tidal and Qobuz apps on same PC took about 1 and feels pretty much instant. It does seem that since Qobuz and the new search algorithms the whole process has got a lot slower. Whist I understand Roon is also looking at my own library as well as the streaming services I hope this is still teething problems and this gets optimized soon. I don’t have a large library only 2500 albums and more core is an i7 with 8GB with a 200mb internet. If I logout of Tidal and Qobuz then search is pretty much instant for the same query so searching the streaming services seems to be the culprit of it being slow or at least a symptom.

Hi @CrystalGipsy,

Do you mind reproducing this issue and then letting me know a timestamp of this slowness? I’d like to see if diagnostics can shed some light on where the issue lies.


Hi Norris a reboot of core seems to have sped things up for now . My worry here is that this slowness happens over time and I should not have to do this to clear it up. I will feedback in a few days to see if it gets slower as the machine had only been up for days prior to this reboot.

1 Like

@noris so 19.10 this evening unbelievably slow to load any artist and its list of album.

Hi @CrystalGipsy,

Sorry for the delay here, can you please let me know what Roon Remote you were using at the time?

– Noris

Android phone this last time. If have noticed that this remote is really bad compared to my android tablet and windows laptop. It takes ages to load albums.

So tonight 23:58 GMT roon cant find The Blue Nile in under a minute, internet perfectly fine to. I have two albums in my local collection…Sorry nut something is really not right.

Hello @CrystalGipsy,

Apologies for the delay in getting back to you here, we have been actively discussing this issue internally to figure out a test plan and gather results for an investigation. We are now asking users to run a test so that we can have a better baseline of factors surrounding this issue.

Can you please this test the next time you’re in this state and respond with the exact local time that you start the test (e.g. 11:38AM) and the time that each step takes:

  1. Run a speed test here and report your results in your response
  2. Open Overview page.
  3. Open Discover page.
  4. Perform a search for “The Beatles”.
  5. Open “The Beatles” artist page.
  6. Open the “Help!” album page.
  7. Start playback of “Help!” (how long does it take before it plays?).
  8. Search for “Daft Punk”.
  9. Open the “Daft Punk” artist page.
  10. Open the “Random Access Memories” album page.
  11. Start playback of “Random Access Memories”.

I’m hoping that we can compare the results from this test to other user reports and if possible identify any common patterns. I noticed in another thread that you mentioned that you have different response times when using Android vs PC, if you can please run this test on both, that would also give us a good data point.


I just had an issue right now on Windows loading Magical MysteryTour from The Beatles which is on Qobuz took at least 30secs to load it. . Help I have in local Library so it loaded straight away, the rest load ok today they have at other times not done.

Speed is 102mb/s with 9ms latency.

Hi @CrystalGipsy,

I’m checking the diagnostics from your core and unfortunately I am seeing a whole lot of NameResolutionFailures:

	Line 246: 04/08 18:21:10 Warn: [tidal/http] GET => NetworkError Error: NameResolutionFailure
	Line 248: 04/08 18:21:10 Critical: [easyhttp] web exception without response: : System.Net.WebException: Error: NameResolutionFailure
	Line 258: 04/08 18:21:10 Warn: [qobuz] [http] error result from http request: System.Net.WebException: Error: NameResolutionFailure
	Line 293: 04/08 18:21:10 Warn: Error in web request NetworkError (Error: NameResolutionFailure)
	Line 294: 04/08 18:21:10 Warn: [tidal/http] GET => NetworkError Error: NameResolutionFailure
	Line 296: 04/08 18:21:10 Critical: [easyhttp] web exception without response: : System.Net.WebException: Error: NameResolutionFailure
	Line 306: 04/08 18:21:10 Warn: [qobuz] [http] error result from http request: System.Net.WebException: Error: NameResolutionFailure

Has anything changed here with regards to how you have your setup configured? I recall that you updated to Roon OS build 174 already but something might still be triggering a DNS issue. If you only reboot just RoonServer from the WebUI, does search work as expected?


No nothing has changed. I did power of the core twice last night as was experimenting with power supplies so that might account for it as it takes a while for my switch to allow connections on boot due to STP, but that time is before I was home unless it’s not counting for daylight saving time. But it was working and connecting to Tidal and Qobuz after the 30sec period.

@noris I have switched dns provider from Cloudflare to Google to see if this changes anything. Will keep you posted.

1 Like

Made no difference, just got slowness again, was attempting to share a link of an album then following your procedure, it got stuck on overview for over a minute returned an error to check my network. Now all is good again, through out this music kept playing but did notice a drop in SQ during this. @noris can you grab a diagnostic around 23.32 GMT

Hi @CrystalGipsy,

I just checked the logs again and it seems like you’re still hitting Name Resolution Failures:
04/11 01:46:06 Critical: [easyhttp] web exception without response: : System.Net.WebException: Error: NameResolutionFailure

Have you made any recent network changes? I can ask the team for some further suggestion here, but something is not quite right on the network side of things if you keep getting these Name Resolution Failures.

I also checked the diagnostics around 23:32 but I could not find anything of note. I don’t see any activity in the logs after you paused Chickfactor - Belle & Sebastian at 23:06.


Hmm very odd how I get issues with search and the ui but nothing is showing up I was listening to that album at that time and I got no response from the UI. Nothing has changed in my all. I was not using Roon at the time of those DNS issues I’ll check my modems log and see if anything shows up as that could be my ISP.

It looks like I lost connection to my isp at the time you see those DNS errors as my modem reports a t3 timeout message. But as I said I was not using Roon at all at that time. It also shows one at 22:01:26 but I noticed nothing happen at that point and no interrupted music which is odd as I was streaming from Qobuz or Tidal at that time.

Hi @CrystalGipsy,

It sounds like your ISP might be having some general network instability. I’m not quite sure that I would expect to see Name Resolution Failures when the modem itself goes down.

I would more expect to see “connection failed” or something similar instead of the Name Resolution Failures. Is it possible that the modem is experiencing heavy delays? What is the exact modem model/manufacturer?

It is possible that Roon already buffered the track and that is why you didn’t notice anything strange. If the ISP instability was temporary, then buffering could proceed as expected but actions that require the internet to function properly (such as search) would be impacted by this.

If you try connecting the Core directly to the router, do you experience the same behavior?