191
submitted 1 year ago by favrion@lemmy.ml to c/fediverse@lemmy.ml

Ugh.

you are viewing a single comment's thread
view the rest of the comments
[-] favrion@lemmy.ml 5 points 1 year ago
[-] RoundSparrow@lemmy.ml -2 points 1 year ago* (last edited 1 year ago)

No. Care to explain please?

On Saturday July 22, 2023... the SysOp of Lemmy.ca got so frustrated with constant overload crashes they cloned their PostgreSQL database and ran AUTO_EXPLAIN on it. They found 1675 rows being written to disk (missive I/O, PostgreSQL WAL activity) for every single UPDATE SQL to a comment/post. They shared details on Github and the PostgreSQL TRIGGER that Lemmy 0.18.2 and earlier had was scrutinized.

[-] sabreW4K3@lemmy.tf 3 points 1 year ago

You've become fixated on this issue but if you look at the original bug, phiresky says it's fixed in 0.18.3

[-] RoundSparrow@lemmy.ml 1 points 1 year ago

The issue isn't who fixed it it, the issue is the lack of testing to find these bugs. It was there for years before anyone noticed it was hammering PostgreSQL on every new comment and post to update data that the code never read back.

There have been multiple data overrun situations, wasting server resources.

[-] sabreW4K3@lemmy.tf 2 points 1 year ago

But now Lemmy has you and Phiresky looking over the database and optimizing things so things like this should be found a lot quicker. I think you probably underestimate your value and the gratitude people feel for your insight and input.

load more comments (9 replies)
load more comments (9 replies)
this post was submitted on 31 Jul 2023
191 points (89.0% liked)

Fediverse

17735 readers
35 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS