Is anyone starting to get a handle on how Mastodon / OSocial hosting requirements scale with use and time?

Traffic / bandwidth, storage, CPU, etc., with some sort of sense of by users, etc., would be interesting.

What's the users * days of a 1 TB storage capacity going to run? Any thoughts on addressing this as individual nodes start accumulating content?

Should content age out? That solves ... several problems.

#mastodon #admins

@dredmorbius ...or keep light stuff local and shove heavy stuff (images, videos) to object storage at utility-billed rates (S3 or a competitor thereto).

Also, feels like various instances have vastly different usage profiles on a per-capita basis. Maybe stuff starts to even out at a large number of users, but dot-social may not have even hit that threshold.

@iansltx I do strongly expect the Law of Large Numbers to be found fully enforced. Though that's under the jurisdiction of the Law of Emergent Properties as well.
@dredmorbius I'd not age out local content for several years at the very least (if ever), though federated stuff could probably be dropped after a shorter time, if the original server is still up.
@dredmorbius This would be a great topic for the Mastodon admins mailing list. Join it if you haven't already.
@Motoma @dredmorbius Similarly, I have the same questions for someone just wanting to run their own instance for themselves (and maybe a small handful of family or friends), but still be connected to the federation.
@Motoma @dredmorbius I want in! Where could I find the mailing list?
@dredmorbius I've been wondering the same thing.