Can you provide a link? Only thing I see on Couchbase is for NoSQL databases.
King
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:
- [email protected]
- 15k subscribers
- 4000 subscribed servers
- 10 votes per subscriber per day
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
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.
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.
The node still needs to receive every subscribed federated action and insert it into the local database. This has to be local to the "main application server". Your proxy servers don't reduce the number of federated actions. It only reduces the number of servers needed to communicate with.
I feel that the bottleneck will be the total number of federated actions, not which servers deliver them.
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.