I noticed a couple of warnings when rebuilding my container: WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128. WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command sysctl vm.overcommit_memory=1’ for this to take effect WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command ‘echo never > /sys/kernel/mm/ transparent_hugepage/enabled’ as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled. My question: are these just some warnings to be ignored? If they should not be ignored (I do feel that my discourse forum is extremely slow), then what exactly should be done? To start with: are these paths and files that the warnings refer to inside or outside the container? If they’re inside, I have no idea how to manipulate them… :confused:

By “sustained”, I meant “more than the occasional “flicker” of a non-zero”. That swap activity, especially when you hit the wordpress page, indicates that you’re swapping like crazy. For instance, at 5000 pages swapped in per second, that’s 20 megabytes per second of data being read off disk. It’s not surprising that your performance is not, to put it mildly, optimal.

The only one of those warnings that could possibly cause problems on a small site is the THP one (and even then only if you’re unlucky). If you ever hit that somaxconn limit you’re doing very well, and overcommit_memory will cause problems on save, but won’t slow anything down. All those referenced paths are on the outer system, not in the container.

[image] codinghorror: 90% of Discourse performance is having a CPU with very fast single threaded performance. The other 10% is having enough memory for the number of maximum concurrent active logged in users your site receives. I’m on a 1 GB DigitalOcean droplet. My Forum currently has three users, two of which are system and discobot. There is no traffic except for my own and the odd web crawler. Still, some pages take way over a second to load. Sometimes 2 or 3. Normal?

That’s very bizarre. I would turn off any third party plugins you have. Digital Ocean isn’t blazing CPU or anything but it is reasonable™ speed.

I installed third party plugins for the first time only this weekend. The speed was slow already before that.

Definitely odd. It is possible you have a bad droplet with a “noisy neighbor” who is eating lots of shared CPU. For Discourse, as I said, most of performance is indeed CPU.

I was getting faster page load times than 1-3 sec on a 1 GB free tier AWS (Ubuntu 16.04) with 1.8 million posts. I’ve bumped it to a 2GB instance, and the page loads are a bit faster. posts:rebake isn’t exactly snappy, but for a sandbox ok. (I changed all 3 of the settings you mention in your first post - this made no difference whatsoever to page loads, or anything else as far as I could tell). Is this an import? What does htop show?

[image] JagWaugh: Is this an import? What does htop show? I don’t know what an import is but here is htop: [image]

Is this just an empty forum with no posts in it, or have you imported or otherwise generated content? [image]

[image] JagWaugh: Is this just an empty forum with no posts in it, or have you imported or otherwise generated content? Yes, it’s basically empty. But there is also a Wordpress site running on the same droplet. But it’s also virtually empty and trafficless. I have a couple of plugins installed though.

Is 1GB RAM enough for both WordPress and Discourse?

Product Support Self-hosting

codinghorror (Jeff Atwood) February 28, 2017, 11:35pm 3

90% of Discourse performance is having a CPU with very fast single threaded performance. The other 10% is having enough memory for the max number of concurrent active logged in users your site receives.

Topic		Replies	Views
Discourse Docker HW reserved/used (CPU, RAM, Disk) and how to manage it Self-hosting server-resources	5	988	May 16, 2023
Discourse not using much RAM Self-hosting server-resources	30	2197	August 8, 2021
3G RAM + 1G Partition Swap - is it enough? Self-hosting server-resources	16	1937	June 4, 2022
How much RAM is required for Discourse? Self-hosting unsupported-install	17	5465	September 18, 2023
Discourse installation has been getting slower and slower and slower Self-hosting server-resources	36	2302	April 15, 2023

Is 1GB RAM enough for both WordPress and Discourse?

Related topics