We’ve taken time to look through available diagnostics and reviewed previous cases concerning ongoing poor performance.
There are always ongoing efforts to debug and improve Roon, and at times, you’ve encountered known slowness related to search indexing or other processes that we have improved.
But we need to set expectations and limits concernign library size and, more importantly, the breakdown of the content within the library. The common factor across all of your poorly performing setups is your library of nearly 850,000 audio files, nearly a quarter of which are entirely unidentified by Roon’s flexible and vast audio analysis service. When that many audio files are atypical - as in, music outside of the metadata and royalty network - then Roon will inevitably perform poorly. That is an order of magnitude of unidentified content for which professional radio station catalog management software will be necessary; it is not an audio consumer use case. Additionally, libraries this customized, on user-end platforms, often source from subdirectory structures wildly outside of standard music industry consumer taxonomy.
This is the reason Roon’s backend services like audio analysis spin endlessly. Anytime you make a change to your library, Roon will attempt to identify the upwards of 150k audio files that are not officially released or recognized music.
Roon is not a professional file management service, nor is it a massive metadata curation service built for a professional radio station. With a library your size, you are simply outside of the consumer audio use case and outside the scope of support.
This thread will move to Tinkering in the meantime.