Much to like about this release but search is tediously slow.
same here 
yup, search terrible here also
They willl! We have to be patient.
I am seeing only CD and MP3 quality for Albums. No FLAC quality appears at all.
Search is now taking a very long time to return results > 30secs and up to 1 min so far which is terrible. The search suggestions in the search bar come up quickly, but even if one of them is selected it is taking ages to get results
Is the DB being reindexed? I have only just upgraded, so if there is a processes running to reindex that would explain.
2 Likes
Same here, based in UK. Search with Qobuz enabled very slow (30s+ and some time outs); without Qobuz enabled it is fast/normal, as also reported in main 1.6 feedback thread before finding this topic. Some more forum members reporting similar issues there.
Still excited about 1.6!
I don’t have Qobuz and Search is still slow but a bit better than an hour ago.
1 Like
Agree. For me, currently from the 30s + region down to 3 to 5 perhaps for some random searches. Much closer to acceptable.
1 Like
yup, my search is speeding up also, now down to <>10secs for most things which is still a bit pants. Must be a db reindexing post 1.6 upgrade?
Also better, between 5 and 10 seconds now.
No…more like massive load on our backend servers due to all of the press/attention post-release. We’ve brought up more servers to cope with the load, and things are in better shape now.
4 Likes
yes they are…thanks for the extra help
Thanks @brian, always good to know the background. I con confirm my searches at around 2secs now.
What, no auto scaling? 
Better shape for sure, but still not “snappy” here
At a certain scale (team size or request count) it’s inevitable. We’re not there. On a normal day we can support everyone on the same # of machines that we need as a minimum for failover/reliability with plenty of headroom. 2-3 days out of the year we need to watch it more carefully.
Auto-scaling is a great way to end up with a giant infrastructure bill that you barely understand + a ton of technical debt because it rewards inefficient code by compensating for it in a way that is totally invisible to the developer.
3 Likes
The winking smiley was supposed to imply tongue-in-cheek… No arguments on the first point… I pity the foo’ that has to decipher and attribute costs for an AWS bill particularly.
I’ve always liked shameback reporting for the “sitck” approach to encouraging efficiency though. Maybe a topping of gamification. I mean… your developers might all hate you and leave, but at least it’s shifted the problem.