I guess this happens when you feed the Roon Server too much 
The final part, which is left out here, is even better. But I reckon that would be too gross.
1 Like
Can you explain why you collect so many songs? As someone stated earlier, you’ll need decades of your life listening non stop to enjoy all of them. I have trouble seeing the attraction of that.
1 Like
Noted. My collection isn’t nearly as interesting: some of those genres perhaps have a barrier to entry? I’d wager that would change now that cost of recording isn’t the primary barrier.
I still say that 4,000 rock albums is plenty! I’ve not even collected half of that, and I’m a rock guy.
It’s funny, but it seems that there are people who just want to test the system to find problems. I have 60,000 songs and I think it’s complicated, and that’s mostly Jazz and Rock. I can’t imagine how to deal with 1,000,000 or more. I believe that many are more concerned with finding problems in the system, testing their equipment, than doing what we really want to do! Listen to music.
2 Likes
My English is not that good, so thank you for your arguments in my favor!
1 Like
That‘s why we‘ve got the more elaborate algorithms according to EBU R 128 to get a better sense of programme loudness range.
Actually, Roon scales wonderfully and works great with large music libraries provided the user understands these few issues:
Large libraries require robust hardware - lots of processing power and lots of memory
Expect the need to close and restart Roon on a regular basis (In my case several times a week). This is due to Roon slowly slowing down the longer one waits between restarts of Roon. Restarting is really not that much of an issue since one can close and restart Roon at times when Roon is not in use, like when playing some vintage vinyl 
Also expect longer start times for Roon - the large one’s music library, the longer it takes for Roon to load into RAM.
Slower search times, although I’m not sure if this an issue related to library size or the interface between Roon and Tidal/Qobuz. Whatever the reason, often searches can be painfully slow, however a Roon restart resolves this issue.
By the way, both Tidal and Qobuz are terrible at providing a full and complete listing of all new releases, with “popular” music releases getting high priority and lesser known artists often no mention. This is one of the main reasons that I added many new releases (which I learn about from different online sources) to my Roon library. If one thinks that my 73K album Roon music library is large, it pales in comparison to the libraries of Tidal or Qobuz. Plus using Roon’s “filter” search is always faster than using Roon’s global (magnifying glass) search.
4 Likes
I think 73.000 is absolutely normal for someone who likes music. Now, 1,000,000, I think that besides taking up more of Roon’s time, by indexing it, it even ends up inducing you to listen to things that wouldn’t be very good, because I imagine that Roon searches your personal library to suggest things that you might like, so I can imagine this working with more than 1 million songs… As for the hardware, this is another fundamental thing in large libraries, I’m running Roon on a Synology DS923+ with 32GB of RAM and all the disks inside the Synology are SSD. And I have a 10GB network (because the DS923+ has a specific 10GB card).
Here I have distribution in 4 environments without any problems.
4 Likes
I am at 104304 Tracks. Not a problem at all. I tripled the RAM in my nucleus. It made it bullet proof. So happy with ROON as of late. All my glitches are a thing of the past!
3 Likes
I agree, how many moans here are someone who runs Roon on an old laptop he had dug out of the cupboard that was no longer in use !!
Hardware is king once you approach 100k tracks especially memory , and dare I say it lose the fear the re-booting !!
In our summer (Johannesburg, South Africa) we get horrendous lightening storms almost daily so its plugs out until it passes . In winter we get no rain at all so I leave the Roon NUC on 24/7 . I notice sluggishness in winter. I restart the Roon server every 2-3 days.
1 Like
Sorry you should not have to restart software or a pc every few days to maintain a music library of any size. Sorry this is just bad resource management of the software if you do. Whilst I agree scale the hardware accordingly it’s obviously Roon doesn’t scale well even with this. Mines struggling with using Roons own tags which I use to identify where my files originate from. I have a relatively small library, plenty of RAM and a fast single core CPU yet it will come to its knees at times, apparently due to my use of tags.
2 Likes
@Jazzfan_NJ has about 73,000 albums (not tracks). Which is great, but much closer to 1 million tracks. 
oh…I didn’t imagine that…
1 Like
All software has its issues, Roon is not without them but I restart daily for other reasons and it gives me a trouble free experience, should I stop doing it so I can suffer along with the others, martyrdom is not for me. I have found a way to co exist with Roon .
Maybe the love affair with Roon is waning again .
We have waited for the dreaded “memory leak” to be fixed for many years and no doubt more years still.
For the delay of a 5 mins restart at a time when its unimportant to me i know what i will be doing
If its of interest , my paranoia with thunderstorms is based on losing a significant amount of kit a few years back due to a direct strike locally. I lost my audio streamer, video streamer, AV amp and a few network bits
Approximately 1,053,000 tracks. “Approximately” because, after all, what’s a few dozen tracks in the grand scheme of all things Roon
I’m not convinced that it’s a memory leak, instead I believe that Roon slows down due to the way the database is being used and almost constantly being updated. Perhaps someone with more experience in databases and with knowledge about the Roon’s database structure and use can help us out.
1 Like
I am somewhat convinced that in most cases (not necessarily all macOS, where Roon memory leaks sometimes seem to be real), people are noticing the phenomenon where an app can use memory to its advantage, but it also can release it when it needs to do other things, and this is not uncommon or even terrible, as long as the program can release memory when other applications need it. That is, just because an application takes a large amount of available memory, that ain’t necessarily a bad thing so long as other applications that need it can claim it back when necessary.
1 Like
Unfortunately my experience is in SQL databases, Roon uses a text based db as far as I know. I am not sure why when the likes of SQLite were around when Roon started but maybe not Soolos
Modern SQL,db engines would eat a million records with appropriate indexing.
I think you are right at the million mark a beefy processor and a plenty of RAM is called for. My NUC is the 10i7 and 32 gb and above say 150k tracks I notice it. I am actively trying the remove duplicates from the library at the moment. That said big boxes also slow life down, anything bigger than say 50 CD
4 posts were split to a new topic: A Database Discussion
My plan was always to have enough music on hand to make a safari through the jungle of music. This is extremely fun to do that. But it‘s always the same in life: you have to work on the base of everything. In terms of a musiclibrary it means you have to make additions to the library as a regular routine. I have fun doing that, but surely listening to music is a bit more fun.
4 Likes