All I am doing is irritating people.

In the Lemmyverse: People seem to enjoy upgrading hardware to huge numbers of cores, adding big-brand front-end commercial DDOS protection, but do not like !lemmyperformance@lemmy.ml discussion on Lemmy itself (eat your own dog-food, developers is not a mantra, as I’ve said here before).

Each new local comment and post on a local server updates 1800 rows in site_aggregates, but there seems no urgency to get the fix out first thing Monday- and stop every large Lemmy server from crashing so frequently. I put “emergency” in the pull request title, leadership edited it out. That says it all. EVERY ONE of the major servers is crashing on my personal visits all weekend, Monday, now Tuesday.

I bring up a direct topic of engineering deletes for scale and concurrency and get push-back from the players on GitHub that that’s off-topic to the delete crashing problem, and I have to lecture them on autism mental differences, which they can’t wait to be irritated by. What a shock, people who find autistic thinking irritating and different from what they think.

It’s the lack of testing and sharing the backend data directly that nobody even noticed these things (site_aggregates has 1700 rows, all getting increments for every new post and comment). And push back on every code that doesn’t pass beautification tests or has an unused testing function in it - it’s like a massive corporation where people only work 9 to 5 and find every excuse to say “not my problem” when it comes to servers crashing every hour.

  • RoundSparrowOP
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    A guy today concluded that the Mali government removed lemmy.ml - not realizing that the constant crashes today continue to be ignored by the Lemmy developers who will not prioritize performance critical crash-fix changes into production servers.

    People have some blind faith that the developers would actually try to fix the server crashing problem other than adding more cores to the hardware. 1700 row UPDATE SQL instead of 1 row, not a Monday priority or a Tuesday one it seems!