Chat

7499 readers

6 users here now

Relaxed section for discussion and debate that doesn't fit anywhere else. Whether it's advice, how your week is going, a link that's at the back of your mind, or something like that, it can likely go here.

Subcommunities on Beehaw:

AskBeehaw

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

remington@beehaw.org

alyaza@beehaw.org

I can fucking relax a little bit (beehaw.org)

submitted 1 year ago by remington@beehaw.org to c/chat@beehaw.org

2 comments fedilink hide all child comments

Over the past 48 hours I have been glued to my screen trying to figure out how to make Beehaw more robust during this Reddit exodus.

My eyes are burning but I am thankful for so much financial support as well as the work of two sysadmins that have given us all a breath of fresh air.

One of the sysadmins was up until 2:30 am helping us out as a volunteer. I am so very grateful for persons such as this.

Thank you all for your continued support and patience.

you are viewing a single comment's thread
view the rest of the comments

[–] veroxii@lemmy.ml 0 points 1 year ago (1 children)

Where are the bottlenecks? Frontend servers or on the db? I have a lot of experience running postgres at scale.

[–] Helix@feddit.de 0 points 1 year ago* (last edited 1 year ago)

I had a first look last night and my preliminary findings are that the DB is actually fine, but the frontend (server.js from Lemmy-ui) and the Pict-rs service are the culprits.

Pictrs doesn't have lots of configuration options and often calls on exiftool to to... whatever. Pictrs also seems to have to deal with a few large pictures, so we reduced the upload size.

Sadly the error users get is some JSON parse error, so this doesn't really tell them the issue and they might try to upload again.

Found a few things which we might want to open a bug report for, but we first have to set up a test server to check my suspicions.