Library about to reach 100,000 tracks

Roon Core Machine

Have a base Nucleus.

Networking Gear & Setup Details

Wired Ethernet to Uptone etherREGEN to TP-Link x60 mesh and dCS Upsampler

Connected Audio Devices

iPad running Roon to TP-Link then on to Roon which passes songs via switch to dCS Upsampler

Number of Tracks in Library

about 80,000 at the moment

Description of Issue

Never clear how many tracks my Nucleus can effectively support given the base memory. I do not use any DSP and typically only have a single Zone running at any time.

Would I benefit by adding memory, and if so what brand, size, etc. And would I also see any benefit in moving to a Nucleus Plus.

Currently I rarely run into problems using the Nucleus in my system, though the library is split across two Western Digital USB attached 8TB drives. Sometimes I’m forced to rescan one of the drives that is nearly full. Seems that Roon must be doing something associated with the space that occasionally causes it to fail to read music from that drive. Wonder if there’s a rule of thumb regarding how much free space is desired on any USB attached or network drives.

1 Like

I would not worry about it at all.
It’s just a guide from Roon more than hard and fast rules.
Especially as you are not using DSP and mostly a single zone I would think you will be good for over the 100k tracks.

First signs might be slow startup or access of albums.
Then if that occurs possibly consider more RAM.
Just go and enjoy your music for now.

1 Like

RAM is easy and cheap. I put two 8GB chips in my Nucleus just for the fun of it. I have no local music files.

Thanks. As I find no information telling me what got shipped with my Nucleus (let alone what is shipped on any model) it certainly would be helpful to understand what specific DIM type and slots are inside, without opening up the unit. Connecting to the Nucleus via my browser all I see is “Roon Database & Settings” 86% of 55 GB Available. No real notion of what that is actually referring to. I’ve no additional storage in the Nucleus than what was in it from day one.
Did you add or replace memory? What is possible and what is suitable.

Sounds like it has a 64gb ssd where Roon itself resides and that will never need changing unless it fails.
I think they shipped with 4gb Ram?
Possibly 8gb but I think was 4gb.

The Roon Nucleus comes with one 4GB chip.

This is what I put in mine, but I don’t remember why I chose this.

What does it support? How many memory slots and types and speeds?

I’m thinking that upgrading to a Nucleus Plus would be a waste, given my use case.

Oops just saw what you purchased.

You can do a search here. There are several threads about upgrading ram on your Nucleus. There are two slots. I think it’s best to use pairs of the same type.

My 2 cents. Buy two modules rather than one big one that’s twice the size. It’s slightly faster that way.

If it’s true that you have a 4GB Module, then buy another 4GB module.

Nucleus is shipped with 4GB of RAM, while Nucleus+ is shipped with 8GB. Replacing them is easy - I have installed 32GB (2x16GB) since the 8GB (Nucleus+) gave issues in some rare occasions when pushing 150.000 tracks. 32GB is very overkill, but then I’m done and this will never be an issue again.

I installed these, worked fine on both Nucleus+ (Rev A) and NUC8i7.

You can also check the Roon Server log (core), this will give an indication of memory consumption if you search for “stats”

08/13 19:40:04 Info: [stats] 26153mb Virtual, 7178mb Physical, 4339mb Managed, 395 Handles, 83 Threads`

If this number goes beyond you available physical memory on Nucleus or NUC with ROCK - the server will crash. Memory consumption will change over time depending what you do (analyzing tracks will consume more memory).

Sorry but how do I do this check? I’m on a Mac.

You need to check logs on your Nucleus. More info can be found here:

  1. Using a Mac, open Finder and navigate to smb://NUCLEUS/Data and use Guest as the username and password. You should then see the RoonServer folder.

Check logs folder under RoonServer. File: RoonServer_log.txt contains the current active logfile.

By searching for “stats” in the log, you will see over time memory consumption (multiple log entries). If that is well below available memory - then no need to worry. Replacing RAM can wait.

And as I mentioned, if you go above available physical memory - the Nucleus will crash and reboot. Nucleus does not use swapfile.

On my system with 193784 tracks - I push slightly above 8GB of memory consumption a few times. Normally it will keep just below.

Thanks. Seems I rarely exceed 2GB of physical. My possible issues have more to do with balancing the number of files across my two USB attached drives. Need to determine the best way of moving these without losing meta data or otherwise corrupting the database. If you’ve any recommendation along those lines, I’m certainly interested in hearing them.

1 Like
1 Like

Hey @stevebythebay,

Ben here with the support team, I wanted to quickly check in on this thread to see if you still needed assistance. By the looks of it, our community experts have provided excellent resources to the questions you’ve provided. They truly rock :metal:

I’ll monitor this thread for your reply in case you do need additional assistance!

I’ve tried using the approach provided but it’s not exactly on point and has proven problematic. Since I’m actually attempting to move albums from one drive folder to another, where both drives are attached to the individual USB ports on the Nucleus, I’ve found it a very slow process, with occasional failures. It would seem that there may be processes involved in Roon that get in the way of a smooth move. If you know of specific things I need to disable during this process that would be fine. Otherwise, I may alter the process by moving albums from the existing location to yet another drive. This would entail shutting down Roon, removing the drive, and plugging it into my Mac along with the other existing drive (with the available space) and basically copying over the files from one to the other and then deleting the albums from the source. Then I’d plug both drives back into the Nucleus and start things up from there. Let me know if this would work properly or if it would do damage to the database that I might not be able to recover from.

Hey @stevebythebay,

Thanks for the information, it goes without saying that I would definitely save a backup before going forward with your migration. As long as you remove your watched folders (or the folders you will be updating) and ensure roon isn’t seeing more than one copy of any file, you should be in good shape :+1:

Another important note mentioned in the article - The best experience will come from letting Roon look at the folders when the files have settled.

If possible, Id be curious to hear about the problems that arose with the approach shared earlier in the thread?

The main problem was that Roon was very, very slow to allow files to get moved from one drive to the other. And many times the process simply stopped. The best way is a 3-way approach, which is what I used. Using an intermediary disk to receive files/folders that I move from one of the attached drives of the Roon Nucleus, followed by moving the transferred files/folders to the other attached drive.

I supposed an even faster method would be to shut down Roon Nucleus and disconnect the drives and do the moves on my Mac.


Yes, always.


This topic was automatically closed after 45 days. New replies are no longer allowed.