On discourse’s forums, I have read 1Gb and max 2Gb of memory should be good, however, those two options do not run my website smoothly and when I run my docker-compose file on 4Gb of memory, it works at around 90-95%, which is a lot. Other things in the docker-compose file are a static HTML website I built and an nginx proxy. Can you please let me know if there is some sorta of trick or settings on discourse to make it run smoother on lower RAM

You need to tweak the amount of workers and the DB buffer. So, the options you would need to tweak would be: db_shared_buffers UNICORN_WORKERS Here you can see the estimates of usage per Unicorn [image] Normal RAM Usage Support Yes, that’s normal. What you can do is tune down the unicorn workers number. In one instance I have: 280MB per unicorn worker 200MB sidekiq 180MB unicorn master I guess going from 4 workers to 2 can shave you some memory. PS: I’m assuming that you are running a ghost town, when you get more users revisit this. Discourse is able to run with 512MB of RAM its not a good experience but it’s possible. You issue is that Discourse reviews the server (as the whole node) resources and plans the resource usage to take advantage of as most resources as possible because Discourse makes the assumption it will run alone.

Here is the docker-compose file. I had to remove some of the images links since I cannot post more than 2, however, this should be good. Where would I place the DB buffer environment variable? version: '2' services: nginx: image: '' #image: 'itshady/nginx' ports: - '80:80' depends_on: - discourse intellectus: image: ' # image: 'itshady/intellectus' ports: - '90:80' postgresql: image: '' environment: - ALLOW_EMPTY_PASSWORD=yes volumes: #- './data/postgresql:/bitnami/postgresql' - 'postgresql_data:/bitnami/postgresql' redis: image: '' environment: - ALLOW_EMPTY_PASSWORD=yes volumes: - 'redis_data:/bitnami' discourse: image: 'docker.io/bitnami/discourse:2-debian-10' #2-debian-10 ports: - '100:3000' depends_on: - postgresql - redis volumes: - './data/discourse:/bitnami' environment: - POSTGRESQL_HOST=postgresql - POSTGRESQL_ROOT_USER=postgres - POSTGRESQL_CLIENT_CREATE_DATABASE_NAME=bitnami_application - POSTGRESQL_CLIENT_CREATE_DATABASE_USERNAME=bn_discourse - POSTGRESQL_CLIENT_CREATE_DATABASE_PASSWORD=bitnami1 - DISCOURSE_POSTGRESQL_NAME=bitnami_application - DISCOURSE_POSTGRESQL_USERNAME=bn_discourse - DISCOURSE_POSTGRESQL_PASSWORD=bitnami1 #- DISCOURSE_HOSTNAME=forums.intellectus.ca - DISCOURSE_HOSTNAME=${FORUM_URL} - DISCOURSE_EMAIL= - SMTP_HOST= - SMTP_PORT= - SMTP_USER= - SMTP_PASSWORD= sidekiq: image: 'docker.io/bitnami/discourse:2-debian-10' depends_on: - discourse volumes: - './data/discourse:/bitnami' command: 'nami start --foreground discourse-sidekiq' environment: - DISCOURSE_POSTGRESQL_NAME=bitnami_application - DISCOURSE_POSTGRESQL_USERNAME=bn_discourse - DISCOURSE_POSTGRESQL_PASSWORD=bitnami1 - DISCOURSE_HOST=discourse - DISCOURSE_PORT=3000 #- DISCOURSE_HOSTNAME=forums.intellectus.ca - DISCOURSE_HOSTNAME=${FORUM_URL} - SMTP_HOST= - SMTP_PORT= - SMTP_USER= - SMTP_PASSWORD= volumes: postgresql_data: driver: local # external: true redis_data: driver: local # external: true discourse_data: driver: local # external: true

If you wrap your raw code with lines that contain only ``` they will be much easier to read. [image] Hady_Ibrahim: image: ‘docker.io/bitnami/discourse:2-debian-10’ #2-debian-10 As step one, I recommend that you use ./launcher to build and launch your Discourse instance. If you want, you can use ./launcher to build it and then launch it with docker-compose (at least I’ve done similar to build and launch Discourse images with kubernetes).

You are using bitnami images and those are completely unsupported by Discourse maintainers and will probably use more RAM than using the Discourse official Standard Installation

why are bitnami images still so popular? answering my own question, it seems like bitnami is the only idiomatic docker option, where the builds are deterministic and centered around ENV variables. Discourse by default uses docker but treats it more like bootstraps for traditional build systems that require you to ssh in and setup/maintain from terminal.

That’s right. If you want help here, you follow the standard install. It you want Help from Bitnami, you can use their image.

I guess you may want to read this: [image] Can Discourse ship frequent Docker images that do not need to be bootstrapped? Development There is this open issue (which I just closed) on Discourse Docker repo asking Discourse should behave like a standard docker image a docker user excepts to be able to run discourse without a special launcher. to define multiple containers (redis, postgres, discourse,..), links and volumes, docker-compose should be used instead. Docker Compose | Docker Docs The question is somewhat misguided, but I would like to address a broader one of Can Discourse ship frequent Docker images that do …

How much RAM is needed to host discourse along with other services?

Product Support Self-hosting

Falco (Falco) November 20, 2020, 3:58pm 3

Can you share the docker-conpose file here so we can make appropriate suggestions?

Topic		Replies	Views
How much RAM is required for Discourse? Self-hosting unsupported-install	17	5454	September 18, 2023
Normal RAM Usage Product Support	8	4281	September 26, 2016
Configure Discourse Docker on servers with more RAM and CPU Self-Hosting docker , how-to	0	6464	August 7, 2014
Oddly high RAM usage with Discourse? Product Support	4	1860	August 24, 2016
Does the server need 2GB of RAM? Self-hosting hosting	19	13500	July 27, 2017

How much RAM is needed to host discourse along with other services?

Related topics