A user, Brandon_Martus, reports persistent 504 Gateway Time-out errors on a Discourse installation after migrating a large vBulletin forum with 2 million posts and high daily traffic. Despite upgrading from 6 to 16 vCPUs on a Digital Ocean droplet, performance remains poor. codinghorror suggests consulting pfaffman, who advises using an “optimized” droplet for better CPU performance and recommends running ./discourse-setup followed by ./launcher destroy app and ./launcher start app to apply the new resources. pfaffman also notes that slow performance may stem from numerous Sidekiq jobs and offers hands-on tuning support. Brandon_Martus thanks the community and plans to try the suggested steps.
I have a new install of Discourse, where I imported a vBulletin forum with about 2 million posts and anywhere from 200-1000 daily active (concurrent) users.
I launched today on a Digital Ocean droplet with 6 vCPUs and browsing the site was pretty rough at the beginning .. very slow, 504 errors, etc.. I resized it to 16 vCPUs, and it’s working better but I am still getting 504 timeouts pretty often.
Is there a guide anywhere on what can be configured in nginx to help use the available resources better?
Load average is still pretty high.
Any suggestions?
Thanks!
EDIT: I realize I didn’t rebuild after resizing, and maybe that will take into account the new resources?