Fresh as of comment time:
huh?
Please explain in detail what "huh" means in this context.
As I said in the comment you replied to: do you know of the history of site_aggregates PostgreSQL table?
What are you asking for? lemmy.ml is the official developers server, and it crashes constantly, every 10 minutes it ERROR out, for 65 days in a row.
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.
Do you know of the site_aggregates federation TRIGGER issue lemmy.ca exposed?
5801ms, terrible
Wow, new:
BACK ONLINE! YEY!
If they are closed, you wouldn’t even be able to submit a registration application.
Show me in the code. Because I have closed the registration on my Lemmy server, and it does not turn off the "Sign Up" link or HTML input fields. But you sure like lies and deception
For the rest of your post, I don’t know what that has to do with people aggreating on LW.
And, factually, the project leaders telling everyone to create 1000 new instances and shutting down sign-up on Lemmy.ml caused more performance problems.
They had a bug in their PostgreSQL TRIGGER logic where 1500 instances were updating + 1 comment and +1 post counting instead of WHERE site_id = 1, a single database row. So each new Lemmy server that went online made the table larger and crashes more frequent on lemmy.ml
The amount of disk writing by lemmy was ignored
Lemmy is written in Rust, I don't think any other platform uses Rust.
Right Now
Working, this comment time