this post was submitted on 03 Jun 2023
55 points (100.0% liked)

Chat

7487 readers
10 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:

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

founded 2 years ago
MODERATORS
alyaza@beehaw.org
remington@beehaw.org
55
I can fucking relax a little bit (beehaw.org)
submitted 1 year ago by admin@beehaw.org to c/chat@beehaw.org
35 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
[–] argv_minus_one@beehaw.org 4 points 1 year ago (1 children)

It’s the thing about databases - what runs fast in dev, doesn’t always translate to real workloads.

Yeah, that's what really scares me about database programming. I can have something work perfectly on my dev machine, but I'll never find out how well it works under a real-world workload, and my employer really doesn't like it when stuff blows up in a customer-visible way.

I decided to write a stress-test tool for my project that generates a bunch of test data and then hits the server with far more concurrent requests than I expect to see in production any time soon. Sure enough, the first time I ran it, my application crashed and burned just like Beehaw did. Biggest problem: I was using serializable transactions everywhere, and with lots of concurrent requests, they'd keep failing and retrying over and over, never making progress.

That's a lesson I'm glad I didn't learn in production…but it makes me wonder what lessons I will learn in production.

[–] darkfoe@lemmy.serverfail.party 1 points 1 year ago

This is why I love canary and mirror releases when feasible. Hard to do with some projects though