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.

  • RoundSparrow@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    What is your server doing?

    Lots of local users logging in and reading content? Federation outbound sending of new content from your server to other servers? Federation inbound?

      • RoundSparrow@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        On my instance, i have a lot of federation incoming messages, subscribed to every large community I could find. And I’m getting posts, comments, votes coming in constantly and the CPU usage for lemmy_server is pretty high/constant. The digital signature and boilerplate federation text is actually high overhead for a single upvote to be processed, etc.

        But CPU usage goes go down if there are no messages for a minute, but 20+ servers sending to my server constantly, it isn’t idle for long.