Day 62, the second major Lemmy runaway SQL statement has been identified in the past 60 days. Lemmy.ca shared about it on GitHub on Sunday, it is now well into Wednesday.

RoundSparrow@lemmy.ml to Lemmy Project Priorities Observations@bulletintree.com · 1 year ago

It was shared on GitHub on Sunday July 22 by lemmy.ca staff. Developers who run the project do not seem to do merges on Saturday and Sunday. I submitted a pull request Sunday evening given the server crash relief this would provide, ready for them first thing Monday. I clearly labeled the pull request as “emergency”.

It is well into Wednesday and merges are being done on new site features for for the past 3 days. Yet, server crash pull request was edited to remove “emergency” from description first thing Monday and sits without any urgency attention.

This is the same pattern I saw for the past 2 months regarding server crashes related to PostgreSQL.

You must log in or register to comment.

Chat

Lemmy Project Priorities Observations@bulletintree.com

lemmy_project_pri@bulletintree.com

Create a post

You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !lemmy_project_pri@bulletintree.com

I’ve raised my voice loudly on meta communities, github, and created new !lemmyperformance@lemmy.ml and !lemmycode@lemmy.ml communities.

I feel like the performance problems are being ignored for over 30 days when there are a half-dozen solutions that could be coded in 5 to 10 hours of labor by one person.

I’ve been developing client/server messaging apps professionally since 1984, and I firmly believe that Lemmy is currently suffering from a lack of testing by the developers and lack of concern for data loss. A basic e-mail MTA in 1993 would send a “did not deliver” message back to message sender, but Lemmy just drops delivery and there is no mention of this in the release notes//introduction on GitHub. I also find that the Lemmy developers do not like to “eat their own dog food” and actually use Lemmy’s communities to discuss the ongoing development and priorities of Lemmy coding. They are not testing the code and sampling the data very much, and I am posting here, using Lemmy code, as part of my personal testing! I spent over 100 hours in June 2023 testing Lemmy technical problems, especially with performance and lost data delivery.

I’ll toss it into this echo chamber.

Visibility: Public

This community can be federated to other instances and be posted/commented in by their users.

1 user / day
1 user / week
1 user / month
3 users / 6 months
0 local subscribers
0 subscribers
37 Posts
0 Comments
Modlog

mods:
adminsag@bulletintree.com