![](/static/253f0d9b/assets/icons/icon-96x96.png)
Ah, you are using pretty different deployment then, even the used postgres image is different then the usual deployment ( pgautoupgrade/pgautoupgrade:16-alpine
instead of postgres:16-alpine
) this might or might not cause differences.
I would try increasing POSTGRES_POOL_SIZE to 10-20, but I am guessing here, the idea being that lemmy is hammering postgres through the default 5 conns which increases CPU but that is a bit of stretch
Check that your account is not marked as a bot (in your account settings).
Accidentally turned that on few days ago and all kind of stuff appeared broken after that.