LIMIT and OFFSET, paging, inside IN filter https://dncrews.com/limit-and-offset-can-work-with-join-f03327fa2ad3
this post was submitted on 20 Aug 2023
1 points (100.0% liked)
Lemmy Project Priorities Observations
5 readers
1 users here now
I've raised my voice loudly on meta communities, github, and created new [email protected] and [email protected] 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.
founded 1 year ago
MODERATORS
Surprised to see local on SJW have zero posts in 1 hour, it's mid-day USA/Canada.
And another thing: https://sh.itjust.works/?dataType=Post&listingType=Local&page=1&sort=TopSixHour
Why not just do what I did with lemmy-helper? Create a time parameter directly.... and it gets us as server programmers out of the equation. Any of the sorts should take a time parameter of old cutoff (even OLD sort order would benefit from "oldest in 6 months" ordering).
Either a unix epoch integer in UTC, or a minutes=x backin time. With a cap of say 10 days.
The routine SELECT queries for listing posts... pulls the private and public keys for both person and community. A lot of text bloat between PostgreSQL and Lemmy's RUST code. I don't think that gets sent down to JSON API client, does it? How does that get filtered out when handed off to JSON?
