Specifically the database backend. Is the polling for notifications causing more database load? From my personal testing, lemmy.ml has the same performance problems with 0.17.4 that it does with 0.18.1 and I haven’t seen anything in the code changes that are that significant with database.

    • RoundSparrowOPM
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 year ago

      Lucky yours did delivery inbound to lemmy.ml - it is the outbound queues of the servers with lots of active communities that is still failing badly in 0.18.0

      At this point, on important topics like this, I go to the original server to make sure I’m not missing posts or comments, as Lemmy to Lemmy is really faltering.

  • RoundSparrowOPM
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Two major problems that I think continues to slow development and rework of the internal performance problems.

    1. Lemmy.world and Lemmy.ml have substanial amount of data in their database. Users, votes, posts, comments - that is difficult to match. New instances for testing start with no data.

    2. Federation activity to peer servers. The big sites have far more servers to share far more communities than any small testing server.

    It would be ideal if there was a open test server that had huge amounts of data in the database and significant federation activity - and opened up the server logs so that we can all get our eyes on what is actually going on within the Rust code.