I’ve been getting a lot of these messages lately:

SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

So I decided to look at the network requests in the browser console. After all, what JSON data was it trying and failing to parse?

Well, turns out that it was pretty much always:

Timeout occurred while waiting for a slot to become available

I don’t do a lot of backend work, but I suspect that the lack of slots might be referring to the server running out of resources to process all of the ongoing user activity concurrently. Could we be running into scaling issues?

  • bielaM
    link
    fedilink
    English
    arrow-up
    97
    arrow-down
    1
    ·
    1 year ago

    A lot of bots were spamming the instance which was causing an IO bottleneck, and thus timeout issues. We’re looking into solutions to limit their impact, such as rate-limiting users. We’re trying to do it in such a way that it doesn’t impact regular users which is why it’s taking a bit longer.

    • jballs
      link
      fedilink
      English
      arrow-up
      21
      arrow-down
      6
      ·
      1 year ago

      Awesome, thanks for the update. You guys rock.

      • imaqtpieMA
        link
        fedilink
        English
        arrow-up
        14
        ·
        edit-2
        1 year ago

        Not in the sense of the other servers that were overtaken by botswarms. But there have been a handful of bots recently.

      • Barbarian
        link
        fedilink
        English
        arrow-up
        10
        ·
        1 year ago

        It’s hard to get a bot onto this instance, but not impossible. Once they’re on here, they can spam out nonsense as fast as the server can take it (hence the rate-limiting solution).

    • [email protected]A
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 year ago

      Yea, rate-limiting per user instead of per IP might be a bit more complicated.
      Appreciate the work y’all put into this.
      You guys seem to handle fine, but if you need to toss a few ideas at a network engineer, ping me.

  • BenFranklinstein
    link
    fedilink
    English
    arrow-up
    23
    ·
    1 year ago

    It’s A LOT worse on lemmy.world, I’d say most of the instances are overloaded that prime time instances.

      • InEnduringGrowStrong@lemm.ee
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 year ago

        Yea I have an account on both sh.itjust.works and lemm.ee
        For the last day or so lemm.ee has been more reliable but otherwise sh.itjust.works was very good too. Ultimately, I feel like this whole thing was meant for having a lot more smaller instances rather than huge ones.

  • southsamurai
    link
    fedilink
    English
    arrow-up
    15
    ·
    1 year ago

    It was the bot bullshit, as others have said. I was kinda expecting it once I saw the posts about the account spamming new C/s, but it hit harder and longer than I thought it would.

  • Contextual Idiot
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    I’ve been seeing that error, and sometimes when I click on a post it sends me to an error page instead. Reloading seems to work, eventually.

    • Corkyskog
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 year ago

      Jerboa app is stable in the way that it just won’t show you shit until it clears the error pages lol

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

    Ya been getting errors and I’m using the world instance. I imagine it’s server capacity and the amount of people posting, joining etc (which is a good thing if that’s the case with people coming over)