still slow at ~10 seconds to complete a search, sometimes a bit more. only started to experience this with 1.8
have a look in your log files to see whats sort of times you are getting?
04/11 11:28:56 Debug: [easyhttp] [27091] GET to https://search.roonlabs.net/1/search?q=The Rolling Stones&count=50&c=qobuz-gb returned after 12261 ms, status code: 200
just shy over 12secs last time I tried.
Same slow search issues here with Roon Rock 1.8 on a i7 NUC and Qobuz.
A search for “Metheny” took abt 15 secs and ended with “no results”.
Needless to say, SAME search on Qobuz (without Roon) was F-A-S-T
Please help a poor LIFETIME subscriber
Thank you
1 Like
Yes just been through the same issue with Roon searches on Tidal, could not find it on Roon.
Searched on Tidal, added it and its in Roon within 30 seconds.
That is another issue in itself, had it happen a number of times for Qobuz. Have another ticket in for it. Not heard anything back on they ticket for a while might have to nudge it.
Roon support already marked this thread with solution, do they read this anymore?
Same problems here, search is slow (as is this forum since 1.8…) Hopefully this is not new normal for both.
@moderators can this threads solution be revoked or get recent posts moved to a new thread as this issue is back
Thanks
2 Likes
Jukka they thought it was linked to server outages, which they fixed, but that only made it slower.
It has been getting worse again for the last week
Still slow as molasses - 12 April, 2021, 0715 EDT (Pennsylvania, USA). Running ROCK on an i7 approved NUC. @support
Just tried searching for “Horace Silver”. I have several local releases on my server and others in my Tidal collection. Search results took about 15 seconds. Not impressed.
Also not impressed with the apparent lack of recognition of this as an issue from Roon Support. I am not particularly interested in individual users who may not have an issue or who may think - subjectively - that waiting several seconds is acceptable.
I don’t think that waiting a few seconds is an issue, let’s not forget that Roon is sending the search query over the internet to Roon, searching multiple databases, then returning and processing that data locally.
It generally takes around 1-5 seconds for mine to return results but it can also take much longer than that i.e 20 - 60 seconds which is not acceptable.
5 seconds isn’t what I’d call fast, but 20 to 60 seconds is definitely unacceptable.
5 seconds isn’t too bad but it’s just long enough to become noticeable. Especially if you have a few searches in a row.
Problem with time is… 5 seconds for a search is really not to long…
But… hold your finger over a lit match for 5 seconds and tell me it’s not too long. 
The good thing is I don’t usually do that while searching for something in Roon…
1 Like
Chris the long search time is calling Roon servers in this case, as you can see in logs it’s the easy http call with the large latency not local processing.
I expect some overhead compared to Tidal and Qobuz servers as they are not querying my own music but it’s become excessive and gets worse during the day, it’s back to a reasonable 3-4 secs right now. Something else I notice is its does seem to vary greatly for different artists. I noticed a search for The Beatles was noticeably quicker than one for the The Rolling Stones. I wondered if this was because of the large body of releases and tried with smaller less known acts with a few releases and they took a long time to.
To be honest I am not interested in the mechanics of how it works, I just would like it to work consistently and within a reasonable time. I should not have to wait 20-30sec to be able to play an album in my collection, I don’t think this is an unreasonable request.
3 Likes
My understanding is that the Tidal & Qobuz searches are not via them but actually a database hosted by Roon as their unique selling point is that Roon adds additional metadata and artist info to this database. If the searches were direct to Tidal or Qobuz they would likely be very very quick as they would be API based.
As I understand it when you search for something there are 3x searches
1x for internet radio stations
1x for Tidal & Qobuz content
1x for local storage content
Once all 3x queries are returned your client collates that info and presents it in the client.
Even if you want to play an album in your local content I think the app still has to go through those 3x searches first.
I’ve seen searches for Tidal & Qobuz take up to 200 seconds to come back in the logs.I suspect that Roon don’t have enough resource in their ‘cloud’ to manage peak periods of people searching etc (at least I’m hoping it’s that rather than a poorly designed DB schema or indexing)
Hopefully if enough people start complaining Roon will investigate and find a root cause.
3 Likes
Yes thats my understanding of it to.
1 Like
Just tried a search for “eurythmics” which came back after 15 secs with no results
Second search for “Eurythmics” also came back after 15 secs with no results
Third search for “eurythmics” came back with artist info after 6 secs
04/13 11:25:14 Debug: [easyhttp] [1265] GET to https://search.roonlabs.net/1/search?q=eurythmics&count=50&c=tidal-ar,qobuz-gb returned after 14616 ms, status code: 200
04/13 11:25:14 Trace: [music/search] [performance] end-to-end search took 14669ms
04/13 11:25:56 Debug: [library] search finished in 14ms
04/13 11:26:11 Debug: [easyhttp] [1267] GET to https://search.roonlabs.net/1/search?q=Eurythmics&count=50&c=tidal-ar,qobuz-gb returned after 14620 ms, status code: 200
04/13 11:26:11 Trace: [music/search] [performance] end-to-end search took 15018ms
04/13 11:26:21 Debug: [library] search finished in 14ms
04/13 11:26:27 Debug: [easyhttp] [1269] GET to https://search.roonlabs.net/1/search?q=eurythmics&count=50&c=tidal-ar,qobuz-gb returned after 5986 ms, status code: 200
04/13 11:26:27 Trace: [music/search] [performance] end-to-end search took 6268ms
I’m in agreement with the consensus that 5 seconds marks a cut off point and anything beyond 10 seconds is painful. I’ve also got a fair collection of searches that took too long, this one was for the final cut a few days ago.
04/10 15:33:07 Debug: [easyhttp] [15603] GET to https://search.roonlabs.net/1/search?q=The Final Cut&count=50&c=qobuz-gb returned after 15100 ms, status code: 200
04/10 15:33:07 Trace: [music/search] [performance] end-to-end search took 15228ms
I’m wondering about a quick bash script to scrape these and total some average stats from the logs.
1 Like