This basically shuts my idea down

it’s not very difficult to modify the code for something like this… and closing off registration wont’ let anyone else login and create new content form your istance.

Personally the load on the major servers by having one more instance that subscribes to everything is why I think people should back off from creating more than the 1500 instances Lemmy network already has. Delivery of every single vote, comment, post 24 hours a day just so one person can read content for an hour or two a day.

That makes sense for email systems where all that content doesn’t have to be sent, but for Lemmy it’s a huge amount of overhead.

When it comes to media attraction, what they call themselves (labels) don’t really matter that much. It’s the praise of strong men, authority, that crosses all mythological media systems. Be it bowing down to a burning bush story, Fox News, or Kremlin.

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.

Is your intention to have local copies of content from popular servers and read it locally? Major communities like news., memes, etc?

Many people seem to think this is offloading the major servers like lemmy.world - but I think the opposite is true in my measures of how lemmy_server performs. There is a lot of overhead to each additional instance in Lemmy 0.18.3 backend. Lemmy code does a lot of work to keep each of these subscribing servers updated with every post, comment, vote, person - attempted in real-time.

BE: 0.18.0

that isn’t that long ago, as in July 1 Reddit API app deadline

A multi-community feature like multi-reddit wouldn’t be that hard to implement. Basically build a subscribe list that isn’t owned by a specific user and come up with a way to link them by name and ID. Being able to share community subscribe and block lists would seem a useful evolution of Lemmy.

So if a home server goes down will those posts disappear from the community server?

terminology wise, “home server of a community” and then there are remote-servers for that community. And Lemmy community/devs tend to call a “server” an “instance”. To answer your question… if a user is on a remote instance from a community, they are reading copies of the content in a local database. If the community home instance goes down, the copies will still be there in the remote servers. However, they are now in an isolated island and none of the other servers will get the new post and comments - as the home instance of a community does distribution. There isn’t any kind of warning indicator that you are on an isolated island.

Nothing disappears, but it is possible to have incomplete replication - have only some of the comments and posts and get an impression that nobody replied or that there isn’t much content.

lemmy.ca staff was so frustrated with performance problems a couple weekends ago they cloned a copy of their database Running AUTO_EXPLAIN revealed site_aggregates logic in Lemmy was doing comment = comment + 1 counting against 1500 rows, for every known Lemmy instance in the database, instead of just writing 1 row.

s in the past hour

Since Saturday lemmy.ml and lemmy.world were not sending content correctly. The problem seems cleared up now.

the module can cause intermittent stuttering, depending on which Ryzen processor you’re using. It appeared when the fTPM was in use, it would access its flash storage via a serial interface, and when doing so, held up activity by the rest of the system.

Nolan pushed the limit of IMAX projectors with Interstellar run time in 2014, he went out of his way to find out what the maximum that could be done with platter modifications, an extra 20 minutes.

do you have any example logs from your postgres instance demonstrating this?

I’ve exposed raw data from my PostgreSQL tables. And every single new comment and post you could see +1 going on every known server. I haven’t updated to 0.18.3 yet, so it’s still there: https://lemmyadmin.bulletintree.com/query/raw_site_aggregates?output=table

(which created rows of that magnitude for updates does sound like federation messages outbound to me)

rows=1675 from lemmy.ca here: https://github.com/LemmyNet/lemmy/issues/3165#issuecomment-1646673946

It was not about outbound federation messages. It was about counting the number of comments and posts for the sidebar on the right of lemmy-ui to show statistics about the content. site_aggregates is about counting.

The issue isn’t who fixed it it, the issue is the lack of testing to find these bugs. It was there for years before anyone noticed it was hammering PostgreSQL on every new comment and post to update data that the code never read back.

There have been multiple data overrun situations, wasting server resources.

Right Now

Working, this comment time

Fresh as of comment time:

rows=1675 was the actual number on Saturday in July 2023.

rows=1675 from lemmy.ca here: https://github.com/LemmyNet/lemmy/issues/3165#issuecomment-1646673946

What if instead of doing 3 things each time you posted a comment, it did 1300 things. And it did the same for everyone else posting a comment.

Yes, that is what was happening in Lemmy before lemmy.ca called it out with AUTO_EXPLAIN PostgeSQL on Saturday, 8 days ago.

Latest, at the time of this comment: still over 4 SECONDS

huh?

Please explain in detail what “huh” means in this context.

As I said in the comment you replied to: do you know of the history of site_aggregates PostgreSQL table?