18
Degraded performance ahead! (burggit.moe)
submitted 2 years ago by [M] to c/announcements@burggit.moe
29 comments fedilink hide all child comments
 

The network Burggit is on is experiencing performance issues. I'd encourage everyone to use shota.nu for right now if you can. I talked to the host about this and evidently it's an upstream issue with the datacenter.

The datacenter is refusing to help out with this and thinks everything is working fine so there's plans for migrating to a new datacenter that are underway sometime soon. So in the meantime, I'm afraid we need to just grin and bear it.

Lemmy errors out if the NFS mount is nonresponsive. It doesn't like not being able to access the huge swathe of pictures that are stored on the server. I've switched the NFS mount to TCP and have it retry the connection every second in an effort to mitigate the severe packet loss.

As I was composing this, the packet loss shot up to 90% so I don't think even that will help...

That's really all I can do for right now. I wish there was more that I could do to resolve this... ๐Ÿ˜”

you are viewing a single comment's thread
view the rest of the comments
[โ€“] 1 point 2 years ago* (last edited 2 years ago) (1 child)

I've figured out the reason, but not exactly.

The cause of this crash has something to do with the specific customization settings of my Sync app.

my Sync backup file. Please try to Restore this backup file to your Sync app and see if you can reproduce the crash

I don't know exactly why the crash only happens on the "Subcribed" feed on Burggit and not in any other lemmy sites

I unsubscribed from one community from rqd2.net and it fixed my issue. But it's weird that that fixed it since Burggit is still federated with rqd2

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] [S] 1 point 2 years ago* (2 children)

    Which community was it? I'm curious to see what data the server tries to return, assuming I can reproduce this on my end.

    E: I noticed that it's running 0.19.0. Maybe try another server we're fed'd with that runs an older version to see if this same behavior happens.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [โ€“] 1 point 2 years ago (1 child)

    !mapmemes@rqd2.net

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] [S] 1 point 2 years ago

    It outright crashes. The logs don't show the instance trying to send anything when it happens, so it's purely a client-sided issue.. Do try another community from an instance that's fed'd that runs an older version of Lemmy to see if it happens with that one too (If you can find one.)

  • permalink
  • fedilink
  • source
  • parent
  • [โ€“] 1 point 2 years ago (1 child)

    Maybe try another server we're fed'd with that runs an older version to see if this same behavior happens.

    I'm subscribed to other communities on the same server so it was weird that subbing to that one specific community crashes the app.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] [S] 1 point 2 years ago

    This appears to be an app issue, then. I scrolled through my subscribed feed on the Boost app and even found a post from that community, and no crashes occurred there. Nothing I can do about it, I'm afraid. I guess report the issue to the maintainer and hope that you don't get banned for the contents of the report (lol)?

  • permalink
  • fedilink
  • source
  • parent