After upgrading Lemmy from 0.18.5 to 0.19.1, the lemmy_server process is taking up 200-350+% of my CPU. Although I haven’t seen it max out my CPU yet, it’s getting dangerously close at times.

Any thing I can do to fix this?

I’d be fine with downgrading temporarily if this will require a Lemmy fix, but I’m not seeing any documentation on how to do that. I’m assuming DB migrations were run between those two versions (which might make that complicated).

  • Charlie FishOPAEnglish
    1·
    6 months ago

    Thanks. It did go down after about 40 minutes or so. It seems like my instance isn’t federating properly now tho. Had to manually call /api/v3/resolve_object with the link to your comment to even be able to reply to it.

    Another example is here you can see that the number of upvotes doesn’t match this.

    Any ideas?