From my experience, this kind of CPU behavior is more likely caused by a server infection or security issue, rather than Discourse itself.
I’ve run into a similar situation before, and replacing the server eventually solved the problem.
From my experience, this kind of CPU behavior is more likely caused by a server infection or security issue, rather than Discourse itself.
I’ve run into a similar situation before, and replacing the server eventually solved the problem.