502 error while opening some user profiles

Maybe also CPU problem. But except when discourse was running some maintenance jobs, we almost never had any problems with performance before. Just now with profile page, so I was thinking on the last update.

But I should say that before trying revert I also tweaked app.yml:

  1. For some reason we were having db_shared_buffers: "128MB", four times less that recommended, probably some legacy from time when I was setting forum first time. I have commented this out, so discourse can setup it himself based on host RAM.
  2. Also I have uncommented db_work_mem: "40MB"

But I did a proper rebuild and tested this first, and it didn’t help us. Only after revert it became better.

Just now tested again without revert just in case, and I can see 502 on profiles again.

If needed I can do more tests with/without patch.

1 Like