We recently included Discourse in our APM, having noticed that performance was beginning to drag a little.
Our existing site is around 15/16 months old and sits on a 2GB/2core DO box (with swap). The instance isn’t massive, we have around 15k threads, or thereabouts.
This seems to be the problem:
I was tempted to sling it onto a larger host, but after a bit more digging noticed that the wp-discourse plugin on our front end site, which is quite large and reasonably high trafficked, is by far the most consuming:
Making anything between 1k and 3k calls per minute. We don’t have debugging enabled, so Discourse shouldn’t be hammered by every post view, but judging from the native performance reports in Discourse the wordpress route is by far the most heavily trafficked, by several orders of magnitude.
Is there any way to throttle this behavior? I can throw more resources at our Discourse instance, or attempt to move it into AWS so it’s adjacent to our front end servers, but at the same time would like to understand the cause before I begin treating symptoms.