Honestly it’s so hilarious to me that matrix solved the problem of having to have a 55TB database by having federation but then decided to have a 55TB database anyway for “numbers go up”
-
Honestly it’s so hilarious to me that matrix solved the problem of having to have a 55TB database by having federation but then decided to have a 55TB database anyway for “numbers go up”
-
Honestly it’s so hilarious to me that matrix solved the problem of having to have a 55TB database by having federation but then decided to have a 55TB database anyway for “numbers go up”
Honestly having a 55TB database is hard fucking work. Even just getting it to that size must have taken uncountable engineering hours when they could have just not.
Genuinely 55TB is 55 times past the “we really need to have a brainstorming session because things are starting to fall apart on their own” threshold.
This is extremely a choice made by the people who ostensibly want to popularise a federated platform.
-
Honestly having a 55TB database is hard fucking work. Even just getting it to that size must have taken uncountable engineering hours when they could have just not.
Genuinely 55TB is 55 times past the “we really need to have a brainstorming session because things are starting to fall apart on their own” threshold.
This is extremely a choice made by the people who ostensibly want to popularise a federated platform.
@rune TBH I think they are doing Something Wrong
. Like this tool exists because the database tends to grow endlessly for some obscure reason https://github.com/matrix-org/rust-synapse-compress-stateOur instance got to like >100 GB with not all that many users (50? not sure). And it just keeps growing if left by itself.
