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…

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 …

[이미지] 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.

Overcommit is irrelevant here, because the problem isn’t processes being OOM-killed prematurely, it’s just trying to stuff ten pounds of allocated memory into a five pound sack. It’s not practically possible to run a Discourse rebuild with overcommit_memory=2, because ember (amongst other things, n…

I’m not sure I entirely agree with your analysis! As I understand it, overcommit allows processes to allocate memory which they don’t touch. It’s not just about OOM-killer behaviour. But as I say, I’d like to run some controlled experiments, that’s a better way to see what does and doesn’t make a …

[이미지] Ed_S: As I understand it, overcommit allows processes to allocate memory which they don’t touch. Partially correct, but even so, it’s irrelevant, because the problem being discussed in this topic is processes allocating memory which they do touch, and touching more of it than the system…

Can you confirm that post @david ’s changes memory requirements are down? We should be in a reasonable state now. The next big jump is going to be pre-compiling and distributed pre-compiled assets, it is a pretty big change to get there but it will erase a big bunch of work from the Internet once do…

[이미지] mpalmer: the problem being discussed in this topic is processes allocating memory which they do touch With respect, I’m not sure about that. I’ve seen log files showing failures in forking. We’re saying in this thread that it’s “memory requirements” but that does - in my view - include …

That was a fresh build without any plugins. I can try another one with a few plugins enabled and maybe temporarily disable swap to confirm that the build goes through (it’ll probably take a few days until I have time, though).

높은 재구축 메모리 요구 사항: 2025년 4월 에디션

지원 자체 호스팅

Olle11 4월 7, 2025, 3:12오전 16

I have 4GB of RAM and many plugins (no swap file of what I am aware of). How many plugins do you have and do you think plain 4GB of RAM is enough?

글		댓글	조회수
Precompiling assets takes 20 minutes Self-hosting server-resources	18	1583	1월 31, 2024
Failed to upgrade discourse instance to Feb 15 2022 Self-hosting server-resources	29	3079	2월 16, 2022
Suddenly boot strapping is failing Self-hosting two-container	25	1368	12월 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	1713	2월 6, 2024
Failed to bootstrap due to out of memory killer Bug	35	2832	4월 29, 2021

높은 재구축 메모리 요구 사항: 2025년 4월 에디션

Related topics