Okay, my question is more theoretical. I can’t predict the popularity of the forum at this time. What I’m trying to understand is, what should I do to mitigate the theoretical possibility of running out of RAM in some scenario. I’m not aware of when Discourse consumes memory the most - either when making backups, or when resizing images, or when updating through the admin console, or … I have no idea.
So my thing was, what swap file should I make to make sure Discourse will not die but just get very slow in case there is not enough memory. In the same time, I found out that there is already a 1G swap partition, so my thought was, what if 3G real memory + 1G partition swap is not enough… should I also create a swapfile of a few gigs with an even lower priority (vs the partition gig). Hope my question makes more sense now.
If it does, then yes. It would be useful to update the installation readme file. Coming from the old days when it was officially mentioned to create a swap file right in the installation readme, I’m now a bit confused whether it is done automatically, or not needed anymore, or any other reason why it was removed form the official howto.
… what about if it detects the 1G one but the partition-based one?
So, the continuation of my question would be, is it a good idea to have two swap areas, one partition-based, and the other one file-based.