• 2 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
  • 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








  • There are/were two reasons why I did that:

    • board manufacturers like to push the juice into the CPU to make benchmarks look good which is dangerous with these power sucking bricks, afaik this might be already patched in recent bioses but I am not risking it/lazy to tweak back
    • depending on the CPU piece you might achieve same performance with less power which is my case, I think I have Core Voltage set to something like Adaptive-0.080 which afaik is still pretty tame and the benchmark scores almost didn’t move










  • taaz@biglemmowski.wintoLemmy Support@lemmy.mlAdd communities
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    11 months ago

    Currently this process is rather painful as there is no way to look at all local communities of remote instance thru your instance and subscribe to them directly.

    Instead there are two ways to get a remote community subscribed locally.

    You can also do the URL-in-search-bar trick with posts and comments to forcefully load/sync them locally.

    Keep in mind that instances will push new community events (upvotes, comments, posts) only when there is at least on subscriber, so in the case you fetch the remote community locally but do not subscribe, it will not be be actively synced and only few posts will be visible (with possibly wrong karma/comment counters and so on).