RAM size requirements #1703
-
|
Can someone suggest the minimum and recommended RAM size? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
Fresh Docker container consumes 125 MB. No files, no connections. |
Beta Was this translation helpful? Give feedback.
-
|
Here's the last 90 days of memory usage for my canary instance: 'Process working set' is the metric I pay closest attention to; it fluctuates based on usage, particularly number of queued and in-process transfers. I wouldn't go any lower than 512mb, and I'd be surprised if it needed more than 2gb to work properly for an extremely active user. |
Beta Was this translation helpful? Give feedback.
-
|
It's worth noting that the underlying Soulseek.NET library and slskd both have been tuned extensively to get the 'total known allocated memory' as low as possible, and ~20mb at idle is very good considering the amount of traffic the application handles to service incoming search requests at a rate of about 30 per second. The 'process working set' metric is largely out of my control given how slskd is written; the runtime and OS dictate that based on how the application uses threads and how the runtime operates. To improve this I would need to reduce reliance on the internal thread pool (meaning no async/await) and that's not a tradeoff I want to make. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
On my setup I have 2 million files in the controller/relay setup both on Ubuntu. Zero files on the controller. Controller is using 2.3GB. Relay is using 2.5GB. Initially I tried running the controller on a computer with 3GB of RAM and the database upload from the relay would fail (though it wouldn't explicitly say out of memory). So maybe 4GB of RAM would be ok on a very lean Linux setup. |
Beta Was this translation helpful? Give feedback.
-
|
Good to know, thanks for sharing. It's working well for you? I haven't gotten a lot of feedback about the relay and wasn't sure. 2 million files is more than I would have expected! |
Beta Was this translation helpful? Give feedback.
Here's the last 90 days of memory usage for my canary instance:
'Process working set' is the metric I pay closest attention to; it fluctuates based on usage, particularly number of queued and in-process transfers. I wouldn't go any lower than 512mb, and I'd be surprised if it needed more than 2gb to work properly for an extremely active user.