late May… what I saw was lemmy.ml turned off new user signup, community creation, and load-shed by letting the server error out.

now lemmy.world is bigger in content and activity but the drastic blocking of incoming links to comments is in place.

I think the number of active users has less to do with the performance problems than the amount of data in the database. The heavy use of JOIN and custom account-specific filters. An account with a large block list and a huge list of subscribed communities likely performs wildly different when listings posts than a non-logged in user.

  • RoundSparrowOP
    1·
    11 months ago

    lemmy servers look so stale on content, even with 0.18.3

    There are so many sort options, but the default “Hot” and “Active” could be more dynamic… trying to list new content if it runs into anything over 3 days. I think having these as parameters per-instance and even moving it to a job outside the main Rust code (or an admin API you can call with different parameters)… there needs to be more experiment. And the 50 limit on community and posts needs to be parameter and not hard-coded.