Skip Navigation

User banner
Posts
127
Comments
598
Joined
2 yr. ago

  • pend my time on Lemmy scrolling “All”, which I think is a pretty common thing.

    There was a lot of advice handed out back in June that the answer to scaling Lemmy was to go create instances. The reason it works is because "All" is empty on a virgin system ;) With no data in the database, the logic Lemmy hands to PostgreSQL works real fast ;)

  • I found the total table update wasn't as bad performing as I thought and the API gateway was timing out. I'm still generating larger amounts of test data to see how it performs in edge worst-case situations.

  • otherwise that would be an easy exploit, just creating a practically infinitely long block list to crash the instance.

    Perhaps you are unaware of just how unstable Lemmy has been since late May.

  • I’m asking because I used to run into the maximum number of blocks on my Reddit client

    I think they used the multi-reddit list as the back-end for subreddit block list. I too ran into the limits.

    I don't think Lemmy has any limit, but performance will likely degrade and it is entirely possible that your personal block list causes overload of servers with lots of data in them.

  • I just set up

    just... it does not backfill previous content and votes. What time window are you talking about here?

    The whole design is not what I would describe as robust and chock full of features. A lot of people have pushed federation as the key to scalability (now with over 1500 lemmy instances online ) when it is one of the least-mature parts of the code and carries a lot of overhead. Having 500 servers all subscribing to the same communities on lemmy.world for a dozen readers is causing problems with outbound distribution.

  • I agree there is potential to reuse the child_count from child/grandchild rows. But there has to be some sense to the order they are updated in so that the deepest child gets count updated first?

  • So it turns out that the query was finishing within minutes and the API gateway was timing out. Too many Lemmy SQL statements in my head. On a test system update of all the comment second run just took under 17 seconds for 313617 rows that has some decent reply depth, so it isn't as bad as I thought.

  • given it traverses all the comment X comment space every time a comment is added.

    The second query I shared is only referenced for maintenance rebuild. The routine update of count does target only the tree that the reply is to:

     
        
     select c.id, c.path, count(c2.id) as child_count from comment c
     join comment c2 on c2.path <@ c.path and c2.path != c.path
     and c.path  <@ '0.1'
    group by c.id
    
      

    I found a particularly complex tree with 300 comments. In production database (with generated test data added for this particular comment tree), it is taking .371 seconds every time a new comment is added, here is the result of the SELECT pulled out without the UPDATE:

    Obviously with the UPDATE it will take longer than .371 seconds to execute.

  • The real war is hate media memes and messages that trickle down to those obedient to voices from the clouds, electric voices these days. In the old days, books that said burning bushes gave out signals.

  • These aren't really what you are looking for in the Firefox console. They tell you the line of code with the error, but not which page has the JSON missing itself.

    I notice your server says Lemmy 0.18.0 - the current is 0.18.4 - any reason you are attempting an older version?

    /api/v3/user/register

    those are the kind of paths you are looking for that can't be reached and your proxy likely isn't forwarding correctly to the lemmy_server Rust app.

  • Instances running lemmy-ui normally publish their list of federated and blocked: https://lemmy.ml/instances

    There might be some scripts or websites out there comparing them.

  • SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data

    This is an error you are getting in your web browser with lemmy-ui? Do you know how to use the console of Firefox or Chrome to look at what API call that error is coming from?

    Caddy as reverse proxy, but I left nginx

    Could be related to your problem... as lemmy-ui doesn't seem to be talking to the API to get JSON responses. I suggest looking at your proxy logs at the instant you press submit on the form.

  • The question seems like a misuse of the word 'federate'.

  • Cool to hear, have a great weekend

  • OK, solved my own issue

    lemmy-ui bypasses the variable if it sees you running localhost 1234, it hard codes 8536

     
        
    export default function getExternalHost() {
      return isBrowser()
        ? `${window.location.hostname}${
            ["1234", "1235"].includes(window.location.port)
              ? ":8536"
              : window.location.port === ""
              ? ""
              : `:${window.location.port}`
          }`
        : process.env.LEMMY_UI_LEMMY_EXTERNAL_HOST || testHost;
    }
    
    
      
  • it has 40 comments total, but the problem is that when I request comments without specifying max_depth, and sort ordered by New, I receive only 10 comments, if I try to specify page, or limit, I get an error {"error":"couldnt_get_comments"}.

    What values are you sending for limit and page? Are you sure they just aren't out of range?

    without specifying max_depth

    I think max_depth has a default, but I don't recall at the moment. Are the 10 comments you do get all trunk level comments, directly on the post?

    My intention is doing something similar to an user pressing “Comments” on front of a community, like calling the community URL

    From what I understand, depth only comes into play when you are viewing the comments of a specific post. If you are just listing comments across multiple posts in a community... they are presented flat. At least that is how lemmy-ui does it when I view comments for a community... which I assuming is using API /comment/list. Am I following what you are attempting?

  • How am I supposed to copy everything from those communities

    what exactly do you mean to copy? messages, posts and comments from other people?

    Are no other servers subscribed to that community and have copies?

  • If what you want to do is “copy all my communities from current instance to new instance”,

    do you mean "copy my list of subscribed communities from one user login to another user login"?

  • Lemmy Server Performance @lemmy.ml

    Lemmy PostgreSQL performance: comment_like & post_like tables have a lot of indexes (5 alone on comment_like), SQL INSERT is taking 0.4 seconds per upvote. Federation incoming lower priority?

    Lemmy Wish list @lemmy.ml

    Beehaw's Lemmy Moderation/Admin feature wish list (lemmy_server)

    PostgreSQL @lemmy.ml

    Lemmy PostgreSQL - can someone please help deconstruct this INSERT SQL: INSERT INTO "comment_like"...

    Lemmy Wish list @lemmy.ml

    Lemmy_server create a local community called "/c/zzz_communities" that gets a new posting automatically when a community is created on that local instance

    Lemmy @lemmy.ml

    PSA: Lemmy 0.18 is rolling out in produciton, lemmy.ml has already been upgraded to BE: 0.18.0-rc.6 - the "websocket webapp" removal

    Lemmy Wish list @lemmy.ml

    Lemmy Wish: "trending communities" should have a dedicated page of output - with the full descriptions and Lemmy Instance hosting the community

    lemmy.ml meta @lemmy.ml

    OBSERVATION: lemmy.ml is now running BE: 0.18.0-rc.6 - not sure on lemmy-ui, but it looks upgraded. The "websocket webapp" change

    Lemmy Server Performance @lemmy.ml

    I suspect the widespread Federation problems and 'nginx 500' errors are connected, Lemmy is swarming comments, likes to other Lemmy servers and causing a Denial of Service on peers

    Lemmy Server Performance @lemmy.ml

    Scaling federation throughput via message queues and workers · Issue #3230 · LemmyNet/lemmy

    Lemmy Server Performance @lemmy.ml

    nginx 500 errors to lemmy_ui webapp users, 0.17.4 era

    Lemmy Administration @lemmy.ml

    Lemmy versus IPv6: over half the Lemmy servers can't reach IPv6!

    Lemmy Administration @lemmy.ml

    : Established instances (not new installs), Community join/subscribe "Pending" for some busy remote servers · GitHub Issue #3203 · LemmyNet/lemmy

    Lemmy Server Performance @lemmy.ml

    Lemmy server admins, please enable pg_stat_statements on your PostgreSQL server so the Lemmy community can better identify the performance problems on the more active sites

    Lemmy Server Performance @lemmy.ml

    PostgreSQL "activity" table grows large: Configurable Activity Cleanup Duration · GitHub Issue #3103 · LemmyNet/lemmy

    Lemmy Support @lemmy.ml

    PSA: The Lemmy federation convention of hotlinking images to other peer federation servers makes it easy for a rogue instance to collect end-user IP addresses & browser strings, don't assume otherwise

    Lemmy Server Performance @lemmy.ml

    Deleting a user with lots of comments (1,59k) modding a few large communities (~20) kills the backend · Github Issue #3165 · LemmyNet/lemmy

    Lemmy Server Performance @lemmy.ml

    Scaling federation · GitHub Issue #3062 · LemmyNet/lemmy

    Lemmy Server Performance @lemmy.ml

    Proposal: Lemmy incoming federation data, queue to database INSERT into comments, votes and other large tables

    Lemmy instances @lemmy.ml

    Lemmy Explorer (lemmyverse.net) to view instances and communities

    Lemmy Server Performance @lemmy.ml

    webapp performance concern - option for admins (and users?) to turn off home page right-column "trending communities" and "subscribed communities"