Hi all, does anyone know why Roon uses so much RAM? I just realised it’s using 8GB of RAM, while at idle - compare that to plex which is using only 500MB and it’s got active connections, harder content videos, pictures and the exact same audio library on top.
I’m guessing poor coding - because it’s definitely not faster than plex - quite a bit slower actually.
Over 50,000 links to albums and 25,000 to artists. A lot of texts and pictures are taken from the net to make everything look great. Here Plex can also do something, but those who come to Roon know the advantages.
Of course, only the right hardware in combination with the operating system and media software ensures a good experience. I used this:
Roon running in Docker (steefdebruijn/docker-roonserver)
Networking Gear & Setup Details
Gigabit Semi-Managed switch
OpnSense Firewall (Running on Qotom Hardware i5 I think)
Gig Fibre Internet
Grandstream 7610 Wifi Access Point (Roon is Cabled though)
Connected Audio Devices
Because it’s probably interesting to others:
Raspberry Pi with HiFiBerry Audio Hat, Fatman iTube, Image Loudspeakers (I wanted small being an apartment dweller - speakers are left over from when I was in a larger house and can’t bring myself to get rid of them because they’re so nice). The Fatman comes to life when not paired to an iPod and everyone comments on the nice colour it adds, not bad for a 13W amp, but I do miss my Arcam - it was just too big for an apartment.
Squeezebox Boom in the Bedroom
Number of Tracks in Library
114931 (A lot of CD Ripping) and a few hdtracks.com purchases later
Description of Issue
Excessive Ram Usage at 8GB
I restarted the docker container yesterday and initially it only ramped up to about 1GB. But, overnight it is now up to 3GB. I can see it is extremely slowly increasing more and more which I assume will be at 8GB in a couple of days. I will keep watching it.
There are a few errors in the logs which seem to be centred on a few files which have corrupted JPEG’s / audio files. They’ve been there for quite a while and one day I’ll figure out how to track them down. But I add them here in case it prompts some thinking. This is not a growing list of files though, it’s an initial list after container start and that’s it. So very unlikely to be causing anything.
Dylan, with all respect, we know a reboot/restart will probably fix it - but only short time. Can Roon finally acknowledge the issue and actually do something about it? And I’m not talking about a built in timed reboot function. I’m sure plenty of people are more than willing to provide evidence and logs
Hi, I restarted it again yesterday, today it is up to 3.5GB in use. Which while not 8GB (yet) is still excessive. This is the kind of memory you need to run a whole OS, not a single application.
There is not analysis happening right now, though I have been adding a number of new tracks, of which clearly will have been analysed. But this is not excessive number of anything - a few hundred or so.
My expectation is that if I leave it for a few days it will keep increasing, but I will monitor it and report back.
At least in my system, the RAM problem does not appear when scanning the library. After initializing / pronouncing Roon Server, the occupied RAM is small. It gradually grows as you listen to music / browse the application and has a boom when backing up the database.
Check this post: Memory leaks on QNAP - #17 by DanielAvasilichioaei