Another discourse mystery

Stephen · October 16, 2022, 7:01pm

1GB is fine for a 4GB system. Make sure you also update unicorn_workers to 4.

Usual recommendation if you were moving between servers would be to re-run discourse-setup which would take care of the above automatically.

github.com/discourse/discourse_docker

discourse-setup

master


      
          }
          
          
          ##
          ## If we have lots of RAM or lots of CPUs, bump up the defaults to scale better
          ##
          scale_ram_and_cpu() {
          
            local changelog=/tmp/changelog.$PPID
            # grab info about total system ram and physical (NOT LOGICAL!) CPU cores
            avail_gb=0
            avail_cores=0
            os_type=$(check_OS)
            if [ "$os_type" == "Darwin" ]; then
              avail_gb=$(check_osx_memory)
              avail_cores=`sysctl hw.ncpu | awk '/hw.ncpu:/ {print $2}'`
            else
              avail_gb=$(check_linux_memory)
              avail_cores=`lscpu --parse=core | egrep -v ^# | sort -u | wc -l`
            fi
            echo "Found ${avail_gb}GB of memory and $avail_cores physical CPU cores"

Topic		Replies	Views
Problem installing Discourse on AWS EC2 instance Self-hosting server-resources	3	562	November 21, 2023
Connection timed out while connecting to upstream on AWS Self-hosting hosting	12	4023	June 28, 2016
Suddenly my server got crashed out of nowhere Self-hosting	8	553	May 15, 2023
Discourse unavailable with high load average Product Support	19	2675	September 5, 2018
Due to extreme load, this is temporarily being shown to everyone... when it's not really the case Self-hosting server-resources	19	2016	July 21, 2023

Another discourse mystery

Related topics