Lemmy’s machine-generated ORM SQL and hand-made flawed PostgreSQL TRIGGER logic is so bad, bloated. The developers on GitHub brag about “high performance”. It’s unbeliable.
In reality, small instances work because it has so many SQL performance problems that it mostly only is stable with little posts and comments in the database. They dd everything they could to avoid using Lemmy itself to discuss !lemmyperformance@lemmy.ml topics and hang out on Matrix Chat to avoid using the constantly-crashing servers they created.
If you go to a server with no users creating comments and posts and only has a tiny amount of data, it does crash a lot less.
Oh geez, why would the Lemmy developers want to do any kind of discussions with you over at the !lemmyperformance@lemmy.ml community, which you moderate?
I see you think that their behavior has only been since June 2, 2023 when I created my account.
The problems with them avoiding Lemmy, “eating their own dog food”, to discuss !postgresql@lemmy.ml have noting to do with me. They hang out on Matrix Chat and do not ask for Rust or PostgreSQL help to their constantly crashing code.
Your style of arguing is to say I wear glasses and have “4 eyes”, childish. You obviously can’t go see they created a new Rust front-end on Github all on your own … and that it was not me personally who created GitHub issue 2910 on June 4, 2023 - almost a month before the Reddit API change.,
Is it the pro-China stance that you like about the developers?
Matrix is a better discussion platform than Lemmy, as one is messaging focused, and the other is a message board. Why are you against Matrix? There’s nothing to discuss on !postgresql@lemmy.world because as far as that community is concerned, it’s dead.
You call me childish when you were the one that retaliated against the developers by creating rubbish issues? Ironic.
What’s with you and your obsession with China? From how much are accusing people of being pro-china, you sure love being on @lemmy.ml, the instance run by the developers.
You’re rocketderp based on your instability I’m guessing? Looks like your the only one that is nonsensical in that thread. Your PR isn’t a PR. You were rushing to someone that was being helpful but you still acted like a child with your advise of GitHub bugs and PRs and not using them properly. The other person in agreement with you at least is calm and rational. I’m guessing you never worked on a group project before or have had anyone disagree with you. Your commits broke the pipeline. Someone even tried calling you down, but you wouldn’t listen.
You aren’t the victim here. You’re the bully.
You’re rocketderp based on your instability I’m guessing?
Yes. My name is Stephen Alfred Gutknecht. It is clearly detailed here on my profile that I am “RocketDerp” on GitHub.
Looks like your the only one that is nonsensical in that thread.
Issue 2910? The word “nonsense” is being discussed about a Lemmy TRIGGER on June 4, 2023.
I’m guessing you never worked on a group project before or have had anyone disagree with you.
You would be guessing wrong. Since late 2019 I am in constant mental anguish and barely surviving. My communications is a constant struggle and I openly disclose this so that it is understood, I am not attempting to cover it up.
I’m guessing you never worked on a group project before
The “i’m guessing” game. And I note you can’t actually cite the Github issues by number (2910) or keep details here in fact. A lot of “guessing” going on.
based on your instability I’m guessing?
“guessing” again. Should I guess you do not know how difficult or easy it is to remove a TRIGGER in PostgreSQL that is causing server crashes?
You aren’t the victim here.
Why do you think this is about “me”? I haven’t donated money to the project or had blind faith in the developers.
You’re the bully.
I’m beyond frustrated that they seem to be going so far out of their way to have servers crash that their motives for doing so need explanation. “Social hazing” is the best answer I can come up with. I’ve now outright asked why they are dong it, because the pattern of behavior with trying to let server crashes has been going on now for months.
I have to admit that it’s amazing the number of people they have attracted with the server crashing. It’s been a social experience in some ways like Elon Musk is doing with Twitter. Perhaps it bothers me when other people actually seem to enjoy it. That seems to be the hiveMind reaction here. In that sense, if it is “social hazing”, it has worked very well.
No.
The feature you suggest be ripped out is one that many people like. I’ve seen people say they hate Mastodon because “Likes” are only counted on the local server and they feel it’s useless. You can’t just suggest rip it out without a fix in its place.
Do we even know the read/write operations of the database are what’s pulling it down when it crashes? Sure it’s not the best code I’ve seen, but on large instances it still manages quite the uptime. Without insight into the cause of the crashes, you can’t honestly say “this, this right here.” Could it help? Probably. Do you need to suggest someone enjoys murdering people because they don’t immediately implement something? Probably not.
Just because you can’t think of another reason why they didn’t listen to you, it doesn’t mean that the one you thought of is correct. That’s not how logic works. It’s narcissistic to believe that you can think of every explanation for something that’s happening.
You’re spamming this all over this thread. Why don’t you go create a PR instead? If you think you have a better solution then go discuss it with the people who have the full context and try to get it fixed instead of complaining here.
Why don’t you go create a PR instead?
It’s amazing how you have fallen hook line and sinker into believing that the problem is difficult to solve. It’s the agenda that is the problem.
They have people like you who will not read actual code to see that they only care about the fact that “Rust is cool programming language” and crashing code doesn’t get any priority.
They even started a new front-end Rust application this month, because they don’t care to bother with the core of the site, PostgreSQL doing INSERT and SELECT statements to load comments.
It’s amazing how you have fallen hook line and sinker into believing that the problem is difficult to solve. It’s the agenda that is the problem.
If the problem is easy to solve, then go solve it, open a PR, and come back here once you’ve done so.
If you’re going to signal that something needs to be done, and you want people to join you in supporting that belief, then actually put something forward that people can get behind. What would me getting angry alongside you actually accomplish? If there was a PR then the community could go and say “Here is a solution, here’s why we think it’s worth merging” and a discussion could actually be had.
Instead you’re just giving rhetoric about how they don’t want to solve this without any evidence, actually creating a PR and having it rejected would be all the anyone needs to see to support your opinion, so go do it.
They have people like you who will not read actual code to see that they only care about the fact that “Rust is cool programming language” and crashing code doesn’t get any priority.
I’ve have merged PR’s in the Lemmy repos. Don’t assume you know anything about me or my position, because you don’t. I don’t have any particular stance on Rust and if this is actually an issue it’s one I’d like to see resolved, so go open a PR and get the conversation started instead of whinging here.
They even started a new front-end Rust application this month, because they don’t care to bother with the core of the site
Are you referring to this repo that Dessalines forked and hasn’t made a single commit against? That hardly seems like they’re abandoning the current frontend and more like a dev messing around with various tech as we all do.
PostgreSQL doing INSERT and SELECT statements to load comments.
If you know what’s wrong, and you know how to fix it, then either put up or shut up. Go make a PR and fix the problem and show us that they rejected the PR because they’re not interested in improving performance. There’s folks like Phiresky actually making meaningful contributions to the backend to help improve Postgre performance, something both dessalines and nutomic have said they’re not well experts in. Be like Phiresky, actually put your code where your mouth is.
Lastly, I don’t know if you were aware of this, but the Lemmy devs don’t owe you anything. Even less so if you’re not actually contributing code or money to help move this project forward.
