We’re still working to find a solution for the posting slowness in large communities.

We have seen that a post does get submitted right away, but yet the page keeps ‘spinning’

So right after you clicked ‘Post’ or ‘Reply’ you can refresh the page and the post should be there.

(But maybe to be sure you could copy the contents of your post first, so you can paste again if anything would go wrong…)

  • vepro@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    I assume that there is something that is O(N), which explains why wait time scales with community size (amount of posts, comments)

    • Slashzero@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Oh, Big-O notation? I never thought I’d see someone else mention big O notation out in the wild!

      :high-five:

      • manitcor@lemmy.intai.tech
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        you are going to meet a lot of OG redditors in the next few weeks. Old reddit had Big O in every post, even posts with cute animals.

  • mykl@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    At least the “reply” button goes away so I don’t end up double- triple- or even duodecuple-posting! Thanks for all the hard work that must be going on behind the scenes right now!

    • cascadingsymmetry@lemmy.world
      link
      fedilink
      English
      arrow-up
      11
      ·
      1 year ago

      I kept getting a timeout message from Jerboa which led me to think I hadn’t been posted. So I ended up submitting the same joke to the Dad Jokes sub three times. Which actually is how dad might tell that joke.

  • Scaldart@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 year ago

    Just hopping into the chain to say that I appreciate you and all of your hard work! This place—Lemmy in general, but specifically this instance—has been so welcoming and uplifting. Thank you!

  • CaptObvious@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    Thanks for posting the workaround and for working to resolve the issue. Lemmy is a great place, and a real breath of fresh air after Reddit.

  • wit@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    Again, thank you for the outstanding work! You are awesome!

    Also, the new icon for lemmy world is great!

  • gkd@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    Been noticing this in the app I’m working on. Pretty much all POST requests fail to return a response and just timeout after 60 seconds. A quick refresh shows that the new items do successfully get created though.

  • Sunforged@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    @ruud@lemmy.world Yo dude, first off huge props and a big thank you for what you have setup. I’ll be donating monthly while I am here. I appreciate that we have an alternative to Reddit at this critical moment in time.

    I do have a question on your long term plans, do you want to continue to expand and upgrade the server, as funding allows, or is there a cap that you will close off the server to new members? Or perhaps make it more of a process to join?

    • Ruud@lemmy.worldOPM
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      Well if all the Reddit users would get over to Lemmy I guess all servers would need to scale up… but I think the server we have now is powerfull enough to grow quite a lot, as long as the software gets tuned …

      • Gompje@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Agreed. Exp Full stack Web dev here. This slowness is clearly a dev issue. The “it keeps spinning” is rarely a db issue or server issue IF the server has power and this one has. This smells to much like something is timing out . I also noticed that when I reply to someone who was logged in from kbin (or even mastodon) it just never ever submits.

        I’m not that familiar with federation itself. But I do know my way around the web. I too hope that they fix this asap. It could even be something like a non sorted query. Or just an endless/to long loop. These are the most typical bugs that happen when there is more data.

        Anyway just my 2 cents. Like I said I’m not that familiar with the Lemmy code.

      • Gompje@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Agreed. Exp Full stack Web dev here. This slowness is clearly a dev issue. The “it keeps spinning” is rarely a db issue or server issue IF the server has power and this one has. This smells to much like something is timing out . I also noticed that when I reply to someone who was logged in from kbin (or even mastodon) it just never ever submits.

        I’m not that familiar with federation itself. But I do know my way around the web. I too hope that they fix this asap. It could even be something like a non sorted query. Or just an endless/to long loop. These are the most typical bugs that happen when there is more data.

        Anyway just my 2 cents. Like I said I’m not that familiar with the Lemmy code.

  • Slashzero@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Have you tried enabling the slow query logs @ruud@lemmy.world? I went through that exercise yesterday to try to find the root cause but my instance doesn’t have enough load to reproduce the conditions, and my day job prevents me from devoting much time to writing a load test to simulate the load.

    I did see several queries taking longer than 500ms (up to 2000ms) but they did not appear related to saving posts or comments.

  • LargeHardonCollider@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Is the slowdown that it the instance has to send out updates about the comment to every other instance before returning a successful response? If so, is anyone working on moving this to an async queue?

    Sending out updates seems like something that’s fine being eventually consistent

      • LargeHardonCollider@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        1 year ago

        Reading more about how this works, sending out updates to each instance shouldn’t block the request from returning unless you have a config flag set to debug source.

        It might be due to poorly optimized database queries. Check out this issue for more info. Sounds like there are problems with updating the rank of posts and probably comments too

        • Ruud@lemmy.worldOPM
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          So it looks like YOU SOLVED THE ISSUE with this reply! This led me to check the debug mode, and it was on! It turned that on when I just sterted the server and federation had issues…

          We no longer seem to have the slowness!!