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

Day 66, perhaps the older servers have data that newer versions do not reproduce

4

1

Day 66, perhaps the older servers have data that newer versions do not reproduce

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

4

It was last Sunday, July 23 that the site_aggregates update of 1500 rows issue was discovered.

Lemmy.ca made a clone of their database.

The UPDATE of 1500 rows in site_aggregates is an example of what keeps slipping through the cracks.

lemmy.ml as a long-running server may have data patterns in it that a fresh-install server does not easily match.

Lemmy.ca cloning a live database to run EXPLAIN was exactly the kind of thing I wanted to see from lemmy.ml 2 months ago.

Chat

RoundSparrowOP
link
fedilink
arrow-up
1·
edit-2
1 year ago
!lemmydev@lemm.ee

Unrelated, but I can never find the name of that community because it is “Lemmy App Dev” but the database key is “lemmydev”, which is what I remember.

Lemmy Project Priorities Observations@bulletintree.com

lemmy_project_pri@bulletintree.com

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
1 user / 6 months
4 local subscribers
98 subscribers
76 Posts
260 Comments
Modlog