Lemmy.ml front page has been full of nginx errors, 500, 502, etc. And 404 errors coming from Lemmy.
Every new Lemmy install begins with no votes, comments, postings, users to test against. So the problems related to performance, scaling, error handling, stability under user load can not easily be matched given that we can not download the established content of communities.
Either the developers have an attitude that the logs are of low quality and not useful for identifying problems in the code and design, or the importance of getting these logs in front of the technical community and trying to identify the underlying patterns of faults is being given too low of a priority.
It’s also important to make each log of failures identifiable to where in the code this specific timeout, crash, exception, resource limit is encountered. Users and operations personnel reporting generic messages that are non-unique only slow down server operators, programmers, database experts, etc.
There are also a number of problems testing federation given the nature of multiple servers involved and trying not to bring down servers in front of end-users. It’s absolutely critical that failures for servers to federate data be taken seriously and attempts to enhance logging activities and triangulate causes of why peer instances have missing data be track down to protocol design issues, code failures, network failures, etc. Major Lemmy sites doing large amounts of data replication are an extremely valuable source of data about errors and performance. Please, for the love of god, share these logs and let us look for the underlying causes in hard to reproduce crashes and failures!
I really hope internal logging and details of the inner workings of the biggest Lemmy instances is shared more openly with more eyes on how to keep scaling the applications as the number of posts, messages, likes and votes continue to grow each and every day. Thank you.
Three recently created communities: !lemmyperformance@lemmy.ml – !lemmyfederation@lemmy.ml – !lemmycode@lemmy.ml
So far, I’ve gotten nothing but replies that do not talk about the failure to show logs and the importance of logging in server applications.
Replies are DEFLECTING the problem
Do I need to keep repeating how much lemmy.ml’s UNAVAILABLE logs of actual failures has been holding back the entire platform and community? this should be blindingly obvious to anyone who has built and supported big client/server apps - what do the error logs say is crashing when you get a 500 error? Issue a BOLO to other server operators on Github or on LEMMY social media platform!
Data integrity, failure to replicate comments to peer instances, is also being ignored. WHY WAS THIS NOT IN THE 0.18 RELEASE NOTES when the application is being pushed as ‘High Performance’ is on the front of the Github page?
Lemmy isn’t being used to even discuss the technical problems of Lemmy. “Eat your own dogfood” isn’t cared about here. The people running servers aren’t reporting major problems and sharing logs to the community.
I’ll repeat it since so many comments DEFECT and use FUD, gaslighting, downvotes, and intimidation to try and shut up the truth.
My name is Stephen Alfred Gutknecht, I don’t HIDE my identity behind anonymous names and deflection. My username is “RocketDerp” on GitHub, and I created !mediascale@lemmy.ml as a subtle message weeks ago. The SUBTLE MESSAGE ISN"T WORKING, GOT THAT?!
The plain-spoken Truth was Posted by me on June 7: https://lemmy.ml/post/1166882