Huge 100K albums database (Roon Requirements)

Hi everyone

I want to use the free trial of Roon but i have a local library on hard disks of more than One hundred thousand albums in FLAC (16-24 bit 44,1-192 kHz) and dsd (dsf) and i don’t know Roon hardware Requirements for this huge database.
I think that from a Money point of view the best hardware solution Is with Windows and not with Apple.

1 Like

People have 5x - that I think I’ve seen

Could’ve been 500k tracks though

With so many albums, your 14 days trial period will be over before Roon has been able to identify them all.

Honestly, in my opinion, Roon is not designed (and capable) of supporting that hugh amount of albums.

And at the very least you will need a minimum of 32 GB RAM and probably lots more, to get Roon working.

the only workaround I see is to work with different folders, and only make 1 folder active at the time.

I have 2 main folders , in my case both active, but I have less than 3000 albums)

2 Likes

I was going to suggest the same thing, break up the storage locations and only enable some of them at a time. Not ideal by any means but that many albums might just grind Roon to a halt. This may play havoc with the DB??

For the trial period I would suggest just add a smaller number of album locations to try Roon out.

Also another note is that you will definitely want to have all endpoints and the server machine wired for this. Having a beefy (high memory, fast CPU, etc) server machine will be needed, also.

Yeah and it really doesnt work that well for a lot of them without compromises being made, one major thing Roon doesnt do well and thats scale.

These are the official recommendations:

People run Nucleus+ with twice the amount stated in the specs, and it may work, but it depends on specifics of the library composition and it may get slow in other cases

1 Like

I would agree with the comments on splitting storage locations. I would import one , trial it.

If happy then get a MONTH subscription to carry on adding other locations.

As to hardware I would use a modern MB Windows Desktop, min 32 Gb RAM (maybe even 64) , fastest processor you can get i7 or even i9. The system C drive MUST be SSD

You are talking a million tracks , that will need horse power. It has been shown to work by other users but only with suitable high power hardware.

Personally I would avoid Roon at all costs if you have 100,000 albums it won’t work well at all unless you make severe compromises. With a collection that size it’s going to have a large portion that isn’t recognised by Roon, as likely there is no metadata available for them in its services. This is then likely to grind to a halt more often than not as it will constantly look for it regardless at regular intervals. It’s not designed to be a repository of such large collections and even less so if its music is not available in its online databases.

3 Likes

100k albums is insane and yeah even the fastest home computer will probably have trouble with this


I have 164K tracks running Roon on a QNAP NAS with Intel i7 and 64 Gb RAM.
Works very well. Fast searching and playing 4 different zones at the same time.
http://audiophraenque.com/

2 Likes

He has 100k albums not tracks big differential there.

5 Likes

What we are talking about according to the OP is 100,000 Albums, which is about 9 times the size of your library.

1 Like

Hi @Andrew_Stoneman, the OP said 100K Albums not tracks.
100K Albums is huge … that’s going to be over a million tracks !!!

IIRC there are a few people running Roon but they have very high spec machines to manage it.
(i9 CPUs, 64GB RAM, fast SSD etc etc.)

I’d say it’s really pushing the boundary of what Roon can scale too and so much is also dependent on the library content. Other’s with smaller libraries but with lots of unidentified albums have experianaced performance issues with Roon.

I’d say at this scale, we are into “tinkering” territory as nothing can be guaranteed.

4 Likes

Maybe @Matz could advise on the specifications of his Roon server and describe his experience (based on track count exceeding 1 million) :innocent:

1 Like

Sorry, I misread.

1 Like

Here a basic calculation

FLAC

QUOTE/
one-minute audio clip using the industry-standard sample rate and bit depth will be around 9mb
END QUOTE/

i take 10 MB / Minute with 80 Minutes / Album and 100 K number of albums

would make a storage space consumption of more or less 80 Terabyte

sorry forum members, this number is unrealistic

if the thread opener has a waste collection of (where ever you get this number legally) MP3 tracks with 128kbps to save disc space there is no need for a roon server

only my last 5 cents, Stefano

Not sure why you’re replying to me with this :man_shrugging:

corrected my post to avoid personal offensive misunderstanding, i am sorry

1 Like

An average album size in FLAC is less than 400mb,

So 400mb x 100,000 = 40tb approx

Very realistic based on todays hard drive costs

I think the use of stolen is quite offensive and I’m not the OP

1 Like

Sorry again,
corrected my post again - i was thinking about older days where it was not likely that this number of items has been acquired legally (without downloads from illegal platforms like Soulseek) but nowadays it may be possible to get it differently

for the calculation this might be helpful

Audio File Size Calculator – Colin Crawley

  • Stefano

P.S.: 40 TB with a decent backup is still no easy thing to get to work for a private person

1 Like