My discourse speed is very slow

our website was so slow we migrated it to a server our website with 4 core CPUs, 8GB Ram, and 8GB of swap memory our website still so slow. i can’t find a way to optimize my site

1 Like

Less advert is good start I think. :slightly_smiling_face:



Wow. You weren’t kidding! It’s completely unusable. I want wasn’t even able to tell what the site was before I gave up.

Single cpu speed and SSD speed are big factors. How fast is the CPU? You don’t have spinning metal disks do you? Have you run discourse setup or changed the memory settings since your changed the amount of ram? Have you tweaked the database settings? You are using a Discourse official Standard Installation?

But since your site is mostly serving ads, it’s impossible to tell what the discourse performance is like.


we are using ssds in our server

I have tested the site with ad blocker and speed is still slow

discourse is installed by digitalocean

no I haven’t


You should either run discourse-setup again or read the comments in app.yml to adjust the memory configuration.

You shouldn’t need any swap.

Is your database very big?

i already have run discourse-setup that didn’t make any difference in speed

yes we have more than 27000 topics on our site

In my experience, Topic List Previews (Plugin) slow down discourse significantly. You may try switch to Topic List Previews (TC), it load much faster than Plugin.

If you disable the Topic List Previews completely, Discourse will speed up several times. :grinning:

We are using a custom plugin to allow topics to still show the cdn images shared on topics , in meta OG if we share them on social media. That cdn support plugin is developed by @fzngagan , faizan, do you have any way to move your written plugin to TLP TC so that site can load faster?

@pfaffman Do you have any specific tech suggestions whatexactly do we need to do to speed up our database and website, I m assuming on it has over 50K+ topics and it’s a high traffic website.

My questions :

  1. Is there any multi threading or parallel CPU or cores configuration we can set up in discourse ? nodebb provides this to cope up with high traffic.

  2. Any server side caching support in discourse , where and how to configure it?

  3. How can we achieve 100% Google page speedscore for

  4. what changes can we do in app.yaml file? we r on 4 Vcpu, 8GB digital ocean droplet.

  5. we r using cloudflare to serve our site. any optimizations we can do there? when I turn on rocket loader of cloudflare, my discourse doesnt work properly and gives errors in js console client side.

  6. any way to auto minify css, js, html, and enable gzip compression on server side?

  7. Please share insights on what optimization you guys have done on to cope up with higher traffic, we can try the same.

  8. Please share insights on optimizations which other high traffic sites on discourse have tried?

Once we are able to speed up our website, we are happy for you to post our site also in successful discourse communities list. Thanks

Well, the number of topics isn’t the number of posts or the size of the database, but that isn’t so big.

The site is down now, so I can’t see the number of posts.

I recommend that you edit app.yml by hand and look at the tuning information there and rebuild. There are several topics that discuss ways to tune the database.

You might also switch to one of the new Digital Ocean faster CPU droplets.

1 Like

Hey, @ahmed_khan1 Don’t risk any downtime, even few minutes down will cost you precious reputation in Google eyes.

Just pay someone professional to handle this for you, once and forever. As I can see your site got a sizeable traffic, so follow the sanity and never go for cheap.

I recommend someone like @pfaffman and @angus.


I’m running a 20,000 Topic site on a 2 Core, 2GB machine with no issues (but may not be as active as yours …)

But yeah, if it’s an issue with running a lot of javascript, then the back end performance is irrelevant.

Have you set this to zero?

That will help a little.

You can move to the TC to speed TLP up, but it does have a rendering limitation in Chromium based browsers (hence why I’ve not decommissioned the plugin so far, Im waiting for LayoutNG to upgrade Grid CSS).


we have a new digitalocean droplet. just purchase it on 1
here’s app.yml

## this is the all-in-one, standalone Discourse Docker container template


## After making changes to this file, you MUST rebuild

## /var/discourse/launcher rebuild app




## visit to validate this file as needed


  - "templates/postgres.template.yml"

  - "templates/redis.template.yml"

  - "templates/web.template.yml"

  - "templates/web.ratelimited.template.yml"

## Uncomment these two lines if you wish to add Lets Encrypt (https)

#- "templates/web.ssl.template.yml"

#- "templates/web.letsencrypt.ssl.template.yml"

## which TCP/IP ports should this container expose?

## If you want Discourse to share a port with another webserver like Apache or nginx,

## see for details


  - "2045:80" # http

#  - "443:443" # https


  db_default_text_search_config: "pg_catalog.english"

  ## Set db_shared_buffers to a max of 25% of the total memory.

  ## will be set automatically by bootstrap based on detected RAM, or you can override

  db_shared_buffers: "2048MB"

  ## can improve sorting performance, but adds memory usage per-connection

  #db_work_mem: "40MB"

  ## Which Git revision should this container use? (default: tests-passed)

  #version: tests-passed


  LANG: en_US.UTF-8


  ## How many concurrent web requests are supported? Depends on memory and CPU cores.

  ## will be set automatically by bootstrap based on detected CPUs, or you can override


  ## TODO: The domain name this Discourse instance will respond to

  ## Required. Discourse will not work with a bare IP number.


  ## Uncomment if you want the container to be started with the same

  ## hostname (-h option) as specified above (default "$hostname-$config")


  ## TODO: List of comma delimited emails that will be made admin and developer

  ## on initial signup example ','


  ## TODO: The SMTP mail server used to validate new accounts and send notifications

  # SMTP ADDRESS, username, and password are required

  # WARNING the char '#' in SMTP password can cause problems!





  #DISCOURSE_SMTP_DOMAIN:    # (required by some providers)

  #DISCOURSE_NOTIFICATION_EMAIL:    # (address to send notifications from)

  #DISCOURSE_SMTP_ENABLE_START_TLS: true           # (optional, default true)

  ## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate



  ## The http or https CDN address for this Discourse instance (configured to pull)

  ## see for details


## The Docker container is stateless; all data is stored in /shared


  - volume:

      host: /var/discourse/shared/standalone

      guest: /shared

  - volume:

      host: /var/discourse/shared/standalone/log/var-log

      guest: /var/log

## Plugins go here

## see for details



    - exec:

        cd: $home/plugins


          - git clone

          - git clone

          - git clone # custom plugin for math JAX support

          - git clone # custom plugin for question and answers and choosing best answer

          - git clone # custom plugin for voting on topics only

          - git clone # custom plugin for automatically posting a yearly topic of forum activity

          - git clone # custom plugin to allow staff to add notes about a user

          - git clone # custom non official plugin for SO style QnA voting on posts

          - git clone # custom official plugin for ads

          - git clone # custom plugin to see who is online

          - git clone # custom plugin for showing topics previews nicely

          - git clone # custom plugin to allow user rating on topics

          - git clone # official plugin for birthdays and join date celebrations

          - git clone # official plugin for saved search notifications

          - git clone # custom plugin to allow users to follow each other

          - git clone # custom build AMP support for HTD

          - git clone # custom for assigning topics to staff

          - git clone # custom plugin for showing thumbnails from CDN images

## Any custom commands to run after building


  - exec: echo "Beginning of custom commands"

  ## If you want to set the 'From' email address for your first registration, uncomment and change:

  ## After getting the first signup email, re-comment the line. It only needs to run once.

  - exec: rails r "SiteSetting.notification_email=''"

  - exec: echo "End of custom commands"

I think you’re running multiple sites on this single instance. Not sure how that would affect the performance issues.

1 Like

we are running only this site on this server.

1 Like

You might bump db_work_mem to 100.

You might have issues with your reverse proxy that is slowing things down.

What does the mini profiler show?

You can also install the prometheus plugin to get some more data.

Have you tried disabling the Who’s Online plugin?

1 Like

I have tried but don’t see a big improvement
here are CPU and memory usage

i have changed unicorn workers to 24
and memory buffers to 4096MB

Have you looked at the browser end?

Granted this is a snapshot but your CPU utilisation looks tiny. I think you are over speccing.

Memory use is only high because of the number of unicorns. Reduce those if it starts to hit swap badly.

I would definitely look at the data retrieval and JavaScript latencies on the development tools of the browser.

Perceived slowness may be down to the amount of work the browser is doing.


From the HTTP headers it looks like you are using Ezoic and Cloudflare. Is that correct? I’m not sure what it does, but that might be another factor for perceived slowness.

My recommendation: Start with a simple setup without any proxies or putting your Discourse behind Cloudflare. Make sure it’s reasonable fast and only then start optimizing by following Enable a CDN for your Discourse or, if you really want to use Cloudflare, Full site CDN acceleration for Discourse.

1 Like

That’s correct, only 1 site, which is is being served on this server via NGINX. Do you have any ways to boost its speed ?