I can relate to this thread completely, and my situation lines up almost exactly with what others are describing — and with what Roon themselves have acknowledged about ARC and large libraries.
My Roon Core runs on a Synology DS1821+ that I’ve upgraded quite heavily: a Ryzen‑based CPU, 64 GB of RAM, 2 TB of NVMe read‑cache, and a dedicated NVMe storage pool used exclusively for the Roon database. The system is extremely fast and stable. Roon Remote is instant, responsive, and never struggles. The server is absolutely not the bottleneck.
My library consists entirely of local files — around 48,000 albums, 587,000 tracks, 18,000 artists, and over 1,000 composers. It’s a huge library, but Roon Core handles it flawlessly.
On the client side, I’m using a Samsung Galaxy S26 Ultra with 1 TB storage and 16 GB RAM, one of the most powerful phones available right now. Despite that, ARC has basically never worked well for me. On previous phones it sometimes wouldn’t even launch. On the S26 Ultra it at least starts, but the experience is still extremely poor: lag, freezes, slow searches, sync issues, and the phone heating up and burning through CPU and battery whenever ARC is running for more than a short moment.
After reading Roon’s own explanation that both iOS and Android enforce strict per‑app memory limits — and that around 250,000 tracks is already the practical upper limit even on the fastest phones — everything makes sense. ARC is simply trying to load and process more metadata than the mobile OS will allow. No amount of server power or phone hardware can compensate for that.
At this point, ARC just isn’t usable with a library of my size. Roon Remote works perfectly, but ARC is nowhere near stable or responsive in its current state, so I’m honestly considering uninstalling it until there’s a major update