Unless I am blind or my search-fu is hugely failing me, I cannot for the life of me find any information on the recommended/minimum specs to self-host the matrix backend services. I’m trying to spin up a VM just to play around with it and see if I like it. Specifically, I’m looking at Synapse or Continuwuity. Any advice?
Looking for vCPUs, memory, storage.
Could you explain what makes an S3 bucket better suited than the default storage scheme? No pressure if not, you’ve already been helpful!
Basically for a cloud provider s3 storage is just any storage. It’s not a disk that needs to be high availability with programs reading and writing to it with an OS on top, its just blobs of data. Images, video, isos, whatever. Its meant for access that is lower than what a VM would need for an active program.
For matrix this is ideal for its content. An image uploaded will be read a fee dozen times, and then less and less until eventually it isn’t really needed ever unless someone scrolls and scrolls up.
So for hosting, if you store that on a disk you’re saying “this is critical to the operation of the software and must be highly available and optimized for vms reading and writing to it.”. Think like m.2 ssds. Blob storage then analogous to us home labbers to throwing it on a giant nas. Its there, may take a bit to load, but its there.
Then s3 has classes too, where if you need your data even less you can pay even less trading off access times, you can get even better rates if you know you need it extremely infrequently, like audit logs. Tape drives are actually used quite a bit for those opt-in low access tiers because if you think about it the data storage is incredibly dense, but opening up a tape can be minutes or longer to access. No problem if you’re pulling up some archive from 20 years ago.