Thanks for checking.
We don't need full database replication. We are just replicating activities that other servers are subscribed to. So the Comments table, only some of the rows will be "replicated". Not sure if/how CouchBase handles this.
Completely off topic. You've linked to another post. I follow it, and end up on a different server, where I don't have an account. I wonder if there is a possible solution.
Buying $10000 of Apple stock in 1997 wouldn't really move the market. TSLA, GOOG, AMZN, MSFT, NVDA, and so on. Lots of stocks where I could buy a small about and get 500x-1000x returns some 10 years later.
I remember reading an issue where the scheduled task to update hot and active was breaking shortly after reboot. So those lists were getting frozen in time, until the next reboot.
That's a good question. Every federated action (post, comment, votes) is transmitted to every subscribed server in real time. Computers are really fast, and should be able to handle thousands of federated actions every second. I don't think we have a good idea on what number of servers are too many.
So a single community with 1000 active users doing 10 likes a day will cause 10,000 inserts on every subscribed server. PG should handle 100's of inserts every second. Something is screwed up in the SQL
I agree here. I don't see Federation scaling without major arch changes. I can't see a server making 50k (subscribed servers) outbound connections for every upvote, comment, etc.
Q: How many Federated actions, on average per user per community per day? Probably a low number, say 5. But 5 * Users * Servers is a huge number of connections once Users and Servers get moderately large. 500k users and 5k servers is 12.5 billion connections, just for one community.
Thanks for checking.
We don't need full database replication. We are just replicating activities that other servers are subscribed to. So the Comments table, only some of the rows will be "replicated". Not sure if/how CouchBase handles this.
Can you provide a link? Only thing I see on Couchbase is for NoSQL databases.
Thanks for doing all this.
Do we have any real numbers from a real server? How many votes are trying to be federated to how many servers?
Just ballparking some approximate numbers:
15000 * 4000 * 10 = 600,000,000 federated actions. That is around 7,000 per second 24/7 for one community.
IMO, this real time federation just doesn't scale. We need to start planning the specs for federation batching.
My instance is missing both comments to this post. https://vlemmy.net/post/376384 versus https://lemmy.ml/post/1605318
Here is an example of the stats being different. Top is lemmy.ml, bottom is vlemmy.net
For anyone else looking, here is the issue: https://github.com/LemmyNet/lemmy/issues/3259
Batching the inserts up only kicks the can down the road a few weeks. We need a 500x improvement in insertion time.
Completely off topic. You've linked to another post. I follow it, and end up on a different server, where I don't have an account. I wonder if there is a possible solution.
Buying $10000 of Apple stock in 1997 wouldn't really move the market. TSLA, GOOG, AMZN, MSFT, NVDA, and so on. Lots of stocks where I could buy a small about and get 500x-1000x returns some 10 years later.
What advantages will traefik bring? Asking, because I know nothing about it.
As I understand it, the bulk of traffic is federation traffic.
I remember reading an issue where the scheduled task to update hot and active was breaking shortly after reboot. So those lists were getting frozen in time, until the next reboot.
That's a good question. Every federated action (post, comment, votes) is transmitted to every subscribed server in real time. Computers are really fast, and should be able to handle thousands of federated actions every second. I don't think we have a good idea on what number of servers are too many.
So a single community with 1000 active users doing 10 likes a day will cause 10,000 inserts on every subscribed server. PG should handle 100's of inserts every second. Something is screwed up in the SQL
I agree here. I don't see Federation scaling without major arch changes. I can't see a server making 50k (subscribed servers) outbound connections for every upvote, comment, etc.
Q: How many Federated actions, on average per user per community per day? Probably a low number, say 5. But 5 * Users * Servers is a huge number of connections once Users and Servers get moderately large. 500k users and 5k servers is 12.5 billion connections, just for one community.
Banks in foreign countries are not covered by FDIC. They don't pay deposit insurance.
How effective is just covering it with cardboard and mulch, instead of desodding?