It feels like the new update is slower than before. Anyone else noticed this?

Could be temporary maybe, or something that will be fixed in a update.

But i get timeouts loading pages even, and that never ever happened before.

  • MacN'Cheezus@lemmy.todayEnglish
    3·
    9 months ago

    Yeah, for me it is Lemmy.world and Lemmy.ml. The latter is also running on 0.19.1, and the former is still on 0.18.5, so the remote server software or version does not seem to be a factor here.

    • tal@lemmy.today
      1·
      9 months ago

      Oh, that’s a good point. We can see server versions elsewhere.

      Here’s a comment from @nutonic@lemmy.ml, one of the lemmy devs, to a remote community on lemmy.world:

      https://lemmy.ml/comment/6801426

      https://lemmy.world/comment/6173591

      That comment appears to have propagated.

      While I cannot say for certain that at that point lemmy.ml had already updated to 0.19.1, it was after lemmy.today had, so it seems plausible.

      So whatever the problem is, I would lean towards guessing that it does not affect all 0.19.1 instances.

      EDIT: Other users are talking about potential federation problems in this thread, where votes appear not to be making it out:

      https://lemmy.ml/post/9624005?scrollToComments=true

      But as someone there points out, the first two users there put up a comment from a 19.1 instance (lemm.ee and sopuli.xyz), and their comments did make it out.

      • MacN'Cheezus@lemmy.todayEnglish
        3·
        9 months ago

        Well, as I just said here, all my comments and posts from the last 24 hours JUST started showing up on those other instances, so perhaps the problem is fixed now.

        Maybe there was some sort of database backlog or something, let’s see what /u/mrmanager says.

        • mrmanager@lemmy.todayM
          3·
          9 months ago

          I think it was Lemmy software stopping to federate for some reason, and after i did a restart of Lemmy, it federated everything in the queue right away. But its worrying that this can happen, and I assume its a bug somewhere hiding in the software still.