In my experience there are few reasons to use a version manager, except for development reasons (i.e. testing on older versions of Node, etc.)
In production, I am increasingly in favour of compartmentalization via containers (or currently, simply separate servers). They can each maintain their own version of Node via the OS package manager, and that's that.
Yep. I concur one hundred percent with the separate vm's for production approach. I don't think I'd utilize containers directly unless I owned the bare metal and needed to leverage that investment for additional duties. And then I'd use a better hypervisor and launch a Linux vm from there. 😜
I sometimes muck about with different nodejs based stuff that wants different versions, requirements, and such and thought it might be nice to forgo spinning up vm's for the quick exploratatories....
None of them seem to want to play nicely with FreeBSD these days though so the question seems rather moot for my use case.
Thanks for the insight @aixnr! We still recommend redis as the default storage engine, especially for small forums, as it was what NodeBB was originally built against. MongoDB is supported just as well as Redis, so there is no fear of it ever being deprecated or considered a second-class citizen when it comes to support.
As for those stats you were asking about:
139.08MB memory used in Redis