Lemmy starts out pretty chill, but the longer it is running, the more CPU it’s using. Until I restart it again, and then the process starts over again. It’s just /app/lemmy that’s eating the cpu cycles. Looks like there are some threads that keep requeueing themselves, until eventually that’s all it’s doing.

Does anybody have any clues or pointers about this?

I’m running 0.17.4, haven’t made the jump yet to 0.18.

  • usernotfoundOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I think that’s more of a client issue than a server issue though.