I have extreme memory growth too but I have a lot of ram. Still the more the memory usage the slower searches go and response times to clicks increase. Roon has been running for awhile now. I can simply kill -9 and it will auto restart. My library is 40K tracks. I am running on a HP ML 350, 24 CPU, 32G ram.
top - 21:14:47 up 194 days, 7:01, 2 users, load average: 0.72, 0.31, 0.34
Tasks: 578 total, 1 running, 577 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.5 us, 0.2 sy, 0.0 ni, 99.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 32736612 total, 1011388 free, 20893128 used, 10832096 buff/cache
KiB Swap: 16515068 total, 15873532 free, 641536 used. 5937140 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
35296 root 20 0 11.4g 5.3g 273336 S 8.9 16.9 1429:09 RoonApplia+
48
What the ram is this high things like adding an album send CPU up. Here is an example:
top - 21:21:32 up 194 days, 7:07, 2 users, load average: 0.30, 0.23, 0.29
Tasks: 574 total, 1 running, 573 sleeping, 0 stopped, 0 zombie
%Cpu(s): 5.3 us, 0.4 sy, 0.0 ni, 94.3 id, 0.1 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 32736612 total, 986744 free, 20882720 used, 10867148 buff/cache
KiB Swap: 16515068 total, 15873532 free, 641536 used. 5947136 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
35296 root 20 0 11.4g 5.3g 280564 S 125.0 16.9 1429:56 RoonApplia+
18
Roon software does not make use of multiple core servers very well, hence the recommendation for i7 CPU and SSD. I believe this is due to the database implementation. I have read other threads of people who have much larger libraries than I do having performance issues. You know millions of rows of data is NO BIG DEAL nowadays. Memory is cheap. Perhaps Mongo would be a good choice.
I am also unsure why library operations affect playback at times on multi CPU servers. Playback should be an entirely separate thread(s) of the application.
Anyway its time to restart by roon core and free some memory for awhile. Despite this inconvenience, I would not trade Roon for anything else. Plus I know that performance is a non-functional requirement for far too many developers.