It looks like 2+2 may not be enough any more… I’m managing a fairly unassuming (no big/fancy plugins, etc) Discourse instance that, as of today, is failing to bootstrap because ember is chewing all the RAM it can find, and all the swap, and grinding the machine into unresponsiveness. Adding another…

[image] sam: it stands 2gb is enough for docker rebuilds Well, it wasn’t for me. Is this compared between basic pure install against real world situations?

Indeed, it’s not perfectly consistent. Even with everything else shut down, it can still fail. Unfortunately we’re fighting a losing battle against modern JS build tooling here. It’s all designed to run on 8GB+ of Ram on modern developer machines, not 1GB VPSs :cry: We do have some solutions in mi…

[image] sam: we do confirm that as it stands 2gb is enough for docker rebuilds, Like Jagster, 2gb RAM + 2gb swap is not, in fact, enough for my CLI-driven docker rebuild. Checking further, the only plugins on this install are docker_manager and discourse-prometheus – neither of which would, …

[image] david: Indeed, it’s not perfectly consistent. Even with everything else shut down, it can still fail. If that’s the case, I think it would still be better to increase the recommended specs a bit. Personally, I don’t really mind adding 2 (or even 4) more GB of swap if it makes rebuilds…

[image] Create a swapfile for your Linux server [image] sam: we do confirm that as it stands 2gb is enough for docker rebuilds, Like Jagster, 2gb RAM + 2gb swap is not, in fact, enough for my CLI-driven docker rebuild. Checking further, the only plugins on this install are docker_manager …

We just landed this commit which should hopefully improve the situation. Please let us know how you get on! (it’ll hit tests-passed in the next ~30 mins) When testing with a memory-constrained docker container locally, I can now get a successful build with -m 1600m. Before this change, the minimum …

I did a test rebuild (fresh install), which went through without issue. Now that machine has 4GiB of RAM (Hetzner CAX11) and a swap file of the same size, so it’s certainly less constraint than the 2+2 GB setup mentioned above. However, swap use was minimal during the whole build and the maximum RAM…

I would quite like to do some controlled experiments, with clean installations and rebuilds, on a variety of setups, and in particular would like to see the difference (if any) of running with vm overcommit, but I’m afraid I’ve lacked the time. (Without overcommit, a large process which forks will …

[image] Ed_S: I don’t think I’ve ever seen anyone volunteer whether or not they are running with overcommit I bet most people don’t. I set it automatically on my installs. I still get that warning about it, though.

Exigences élevées en mémoire pour la reconstruction : édition avril 2025

Soutien Installation

Matthias_Schuster (Matthias) Avril 4, 2025, 12:21 9

Le zram n’aurait-il pas de sens ?

Sujet		Réponses	Vues
Precompiling assets takes 20 minutes Self-hosting server-resources	18	1432	Janvier 31, 2024
Failed to upgrade discourse instance to Feb 15 2022 Self-hosting server-resources	29	2948	Février 16, 2022
Suddenly boot strapping is failing Self-hosting two-container	25	1137	Décembre 30, 2022
Upgrade from 3.2.0.beta3-dev to 3.2.0.beta3 failed due to out of memory Self-hosting server-resources	18	1589	Février 6, 2024
Failed to bootstrap due to out of memory killer Bug	35	2622	Avril 29, 2021

Exigences élevées en mémoire pour la reconstruction : édition avril 2025

Sujets connexes