Is this good or bad ?
My roon is slow and the last update did not hep much , still no update for nearly 3 months.
Is there a major update on the way is that why?
If so I hope it doesnt make roon slower than it already is
You can’t expect updates with additional features without incurring some performance hits if your platform is marginally spec’d - not saying yours is but you leave the question of your systems current spec undisclosed. Hard for anyone to offer any suggestions without some specifics.
There is no free lunch…its the same thing for OS’s and Apps alike.
1 Like
Ouch, that stings.
In general you are right, but if I stop a not responsive query after 20 sec and then the subsequent (identical) one takes only 1 sec, it’s not a matter of system specs.
It’s a matter of bugs.
…or I/O glitches
Then you should raise a support ticket in the #support threads and wait for some response from Roon.
Aside from edge case features that only a few would use, are there truly any glaring issues or missing capabilities?
In my opinion, no.
I hope the Roon team resists temptation to start cramming in features for the sake of adding features.
2 Likes
Doesn’t this Indicate a caching effect going on in Roon’s servers? The query is not stopped when you stop it and so the answer is found in the background, ready to be provided when next asked.
Just because your Roon version hasn’t upgraded doesn’t mean improvements aren’t happening. The Roon infrastructure that we never see is getting worked on and those changes aren’t immediately visible to us (see below). Sure, there are other things we’d like to see on our Roon app either as new features or performance improvements. But based on Brian’s comments I wouldn’t read much into the release schedule.
brianBrian LuczkiewiczRoon Labs: CTO
There are lots of things going on to improve search. It’s not one issue, and not all of the stuff that is impacting search is specific to search. I can elaborate on some of it…
In the most recent release, we rolled out a significant optimization for how the core handles out-of-library objects–search is a heavy consumer of this infrastructure. This fixed a primary cause of slow searches at that point in time and also reduced Roon’s background CPU usage in general.
Once the dust settled on that release (2-3 weeks ago), it enabled us to survey what remained. At that point, we discovered a root cause of 30-60s searches/timeouts, developed a fix last week, and rolled it out at the beginning of this week. As far as we can tell, that failure mode is over, and the next goal should be about getting currently 1-5second searches into the hundreds-of-milliseconds range.
The search index itself is adequately quick. Most of the time goes to either results processing, rights processing (determining which content you are able to see based on the TIDAL/Qobuz regions you are logged into), and formatting the results for transmission to the app. Search is one of the heaviest pages in the app and leans hard on a lot of infrastructure.
This infrastructure performs the same as it always has, but search has a much tighter responsiveness expectation than other pages, so it is forcing us to rethink a lot of how that old stuff was built. Much of this stuff was built long before we formed Roon, some as early as 2012, and at that time we were building a different product with a different set of goals. Re-building a lot of this is healthy and necessary, but not instantaneous.
Anyways–that infrastructure is about halfway through a ~6 month optimization project. The first half of the work is poised to roll out next week, and speeds up the most expensive steps by about 2x. The second half of the project is underway, and should yield a similar scale of improvement.
This project also enables us to deploy a more sophisticated worldwide caching system that will help reduce round-trip latency for everyone when loading data in Roon. This project is not search-specific–it will affect almost every screen in the app that loads data from our servers–but as one of our heaviest screens, search should benefit substantially.
We have another project in flight to multiply the capacity of our search backend by 2-3x and design a faster and better indexing process. This will help the speed of new releases getting into the search index. In parallel, we are also working on the latency of new releases showing up in Roon in general, both by coordinating with upstream providers, and by re-organizing some of our internal processes. The difference will be substantial once all of that work flows through. The larger-capacity search backend will also enable us to make the searches themselves more expensive–enabling us to re-attempt fuzzy matching, or otherwise improving the queries/results quality by spending more compute resources per search.
There are a collection of smaller projects related to search–building a better benchmark for search results quality, and tracking down a few minor bugs. This stuff is also in flight.
There is so much going on here that I’m sure I’m forgetting something…these infrastructure/backend projects take a lot of time and do not make for splashy product releases, but we have to do them. Roon has to get faster, and it has to do that while our user base continues to grow rapidly, and without breaking too much along the way. Not an easy problem, but one that has consumed a lot of our attention in the past few months.
1 Like
I don’t think so.
Anyway, Roon is a great software and I’m happy with it. But, honestly, the search functionality is really terrible, both from performance and functional points of view.
1 Like
This is the longest time without a major update i guess