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

  • RoundSparrow@lemmy.mlOP
    1·
    1 year ago

    Lemmy community is an echo-chamber of people ignoring the fact that the developers bold claim “HIGH PERFORMANCE” on the GitHub project page without any validation.

    Not one person was willing to stand up and say “this is LOW performance, amature mistakes in not having caching of” SELECT "local_site"."id", "local_site"."site_id", "local_site"."site_setup", "local_site"."enable_downvotes", "local_site"."enable_nsfw", "local_site"."community_creation_admin_only", "local_site"."require_email_verification", "local_site"."application_question", "local_site"."private_instance", "local_site"."default_theme", "local_site"."default_post_listing_type", "local_site"."legal_information", "local_site"."hide_modlog_mod_names", "local_site"."application_email_admins", "local_site"."slur_filter_regex", "local_site"."actor_name_max_length", "local_site"."federation_enabled", "local_site"."federation_worker_count", "local_site"."captcha_enabled", "local_site"."captcha_difficulty", "local_site"."published", "local_site"."updated", "local_site"."registration_mode", "local_site"."reports_email_admins" FROM "local_site" LIMIT $1

    It’s outright disillusion that people labeled it “HIGH PERFORMANCE”.

    The Lemmy community sure have the bullying part and shit-talking peer applications down on Social media, but the project internally shows that there is no street credibility when it comes to “HIGH PERFORMANCE” bold claims against even the basic email systems.

    Lemmy admins who won’t use Lemmy to talk about and try to solve their hourly server crashes .

    Gaslighting me about it was way more serious than me speaking up bravely about the problem. Intimidation tactics you are showing to me say a ton about why you have these problems in the first place. The lack of concern for the end-user data being lost also speaks volumes as to priorities.