I’m not sure when it started, but at some point in the last few weeks, presumably after a Discourse update, the site started to feel a bit sluggish. We’ re running 3.4.0.beta2-dev. I noticed that the server instance had almost no free memory, so I rebooted it. After Discourse started, memory use wa…

Free memory is a very slippery concept - the one sure sign of too little memory is paging activity. free or free -h will give you a snapshot vmstat 5 5 is very useful to see how things are going, including paging activity.

total used free Mem: 1.9Gi 1.5Gi 73Mi Swap: 2.0Gi 54Mi 1.9Gi procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu----- r b swpd free buff cache si so bi bo in cs us sy id wa st 0 0…

certainly that looks fine at present - no activity in si and so, which is paging, and also very little disk traffic, which is bi and bo. what linux does is use free memory for disk caching, so it’s not bad to see free memory go low. The output of free shows available RAM, the man page says: avai…

Okay, thanks. Possibly the sluggishness was unrelated to what appeared to be a low memory situation. I will continue to monitor this.

It’s still possible that something is gradually getting bigger. This is one of my tactics to see what’s going on: # ps aux|sort -n +5|tail systemd+ 1659 0.0 1.3 904384 54588 ? S 16:44 0:00 /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main root 830 0.0 1.6 …

If it’s easy to monitor CPU and (disk) I/O activity, I’d recommend watching those, rather than memory use. Especially I/O. If CPU is low and I/O is high, and the forum is slow, that could indicate an impactful shortage of RAM.

A couple of reasons, other than a bug, for a site becoming sluggish: one is gradual increase in users, user activity, database size; the other is Discourse getting ever larger as it develops, adds features, updates software components. But it is worthwhile to keep an eye on responsiveness, and on w…

Thanks for sharing your observations. I’m seeing much the same, except that we’re using a 2 GB instance, so there’s less headroom. Also, thanks for pointing out that some measures of ‘free’ and ‘used’ memory are not necessarily helpful. When I last rebooted the instance a few days ago, the initial …

Upgrading Discourse was becoming a chore due to memory issues, so we finally upgraded the virtual machine from 2GB to 4GB. Since then, memory use has stabilized.

재시작 후 메모리 사용량이 서서히 증가합니다

지원 자체 호스팅

jrivettcsa (Jeff Rivett) 7월 6, 2025, 1:19오후 10

메모리 문제로 인해 Discourse 업그레이드가 번거로워졌고, 결국 가상 머신을 2GB에서 4GB로 업그레이드했습니다. 이후로 메모리 사용량이 안정되었습니다.

글		댓글	조회수
Discourse not using much RAM Self-hosting server-resources	30	2003	8월 8, 2021
Discourse installation has been getting slower and slower and slower Self-hosting server-resources	36	1958	4월 15, 2023
Memory is running out and Discourse stops working Bug	74	14796	2월 17, 2015
Memory creep in last couple of updates Self-hosting hosting	27	3017	5월 21, 2019
Discourse Docker HW reserved/used (CPU, RAM, Disk) and how to manage it Self-hosting server-resources	5	937	5월 16, 2023

재시작 후 메모리 사용량이 서서히 증가합니다

Related topics