I currently have over 1 million tracks, although about 15% of them are from Qobuz and Tidal, with Roon running on a fairly powerful desktop Windows 10 PC. Roon uses approximately 15GB of the 64GB memory.
What one can expect with a +1,000,000 track library is for Roon to sometimes run quite slowly which means that it’s time for to close and restart Roon, including Roon Server. I close and restart Roon about 3 times a week. Restarting Roon takes about 5 to 10 minutes. Once running the large library size doesn’t seem to affect the speed of Roon until Roon has been running for several days and then I know that it’s time to close and restart Roon.
That is interesting to know thanks.
My Roon is sitting at around 8GB of memory on DietPi for a 92K library (up for about a month).
Good to know that I am safe to Keep buying more music and that the 16GB should last me quite some time yet
When running Roon on a Windows PC there more to it than just how memory Roon is using. I used to have only 32GB of memory, which with Roon using 15GB to 16GB of the 32 GB of memory, would appear to be enough memory but this was not the case. When I had only 32GB of memory installed, overall with Roon running the PC was using close to 90% of the available memory and many programs, including Roon, ran slowly and erratically. Once I increased the memory to 64GB, where now the PC typically is using about 40% to 45% everything runs much more smoothly.
Of course running Roon on other operating systems will yield different results.
Assume the average length of a song is 3 minutes, 1 million songs are 3 million minuets. That is 50K hours. If you listen them non-stop 16 hours a day (8 hours for sleep), it will take 3125 days or 8.5 years to listen all songs once…
However, one might have albums in the library for purposes of documentation. Because if they are in the library you can see them in Focus, when otherwise you wouldn’t. E.g., if you want to look at a history of rock music in the 70ies, then you can see them there. I, for one, do this with historically significant albums even though I might never listen to them again.
It’s a result of Roon’s two-class system for in-library vs not-library albums.
It is always interesting to see people’s completely different approach to their personal library and to roon browsing. Every time I meet roonies IRL I have this ´you are using it like THAT?´ moment, and that is absolutely fine.
I personally gave up on the idea of being some kind of librarian or historian. I once liked the idea of having everything of any significance at hand but I noticed that it makes me loose focus and overview as well being obsolete by the fact you can have almost everything from a streaming service such as Qobuz.
So I rather came back to the idea of having a personal library which I can oversee and which represents the music I really like and will probably listen to at a certain point in time.
Not albums but items, it seems… So for example an album favorite is one item (it points to the album) but if you favorite a track, it also counts as one item. Max is 9,999. Seems like someone made the typical “Noone will ever need more than 640KB”. Looks like Spotify had the same limit (I wonder if there’s cross-breeding between those teams). Spotify however, removed this limit, and argued it was a difficult architectural change! I cannot imagine this.
For me it’s not about the fact that you can have everything on Qobuz or about being an exhaustive librarian. I also prefer a personal library, or rather my personal view on music. (And I have only 50k tracks in the library).
Qobuz has everything but you can’t see a structure. Roon lets me add those albums from Qobuz to my library that are significant for my personal view of a musical period that I’m interested in. So I‘ll add, for instance, some seminal 70ies rock albums to my library even if I’m unlikely to listen to them (again), but if I look at 70ies rock then it shouldn’t look like they never existed and it should reflect my personal view of the period.
Hence the „listening to all tracks in a big library takes such and such crazy amount of time“ doesn’t always reflect how it’s used.
)
