Lemmy

12572 readers

1 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago

MODERATORS

nutomic@lemmy.ml

168

What is the long-term storage plan for Lemmy instances? (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by Kalcifer@lemmy.world to c/lemmy@lemmy.ml

77 comments fedilink hide all child comments

Over time, Lemmy instances are going to keep aquiring more, and more data. Even if, in the best case, they are not caching content and they are just storing the data posted to communities local to the server, there will still be a virtually limitless growth in server storage requirements. Eventually, it may get to a point where it is no longer economically feesible to host all of the infrastructure to keep expanding the server's storage. What happens at this point? Will servers begin to periodically purge old content? I have concerns that there will be a permanent horizon (as Lemmy becomes more popular, the rate of growth in storage requirements will also increase, thereby reducing the distance to this horizon) over which old -- and still very useful -- data will cease to exist. Is there any plan to archive this old data?

you are viewing a single comment's thread
view the rest of the comments

[–] Legarth@lemmy.fmhy.ml 3 points 1 year ago (2 children)

Isn't it mostly pictures and movies taking up space, posts and comments that is just text doesn't take up much.

I would be fine with text is forever but pictures and movies are deleted after time.

[–] WhatASave@lemmy.world 6 points 1 year ago

Just think of all those old, helpful forum posts from years past with tinypic and Photobucket links that are dead. I agree memes can probably die out after time but anything informative would be bad to lose imo

[–] freeskier@centennialstate.social 5 points 1 year ago

For large instances pictures is probably the bigger consumer of space, but for small instances the database size is the bigger issue because of federation. Also, mass storage for media is cheap, fast storage for databases is not. With my host I can get 1TB of object storage for $5 a month. Attached NVMe storage is $1 per month per 10 GB.

For my small instance the database is almost 4x as large as pictrs, and growing fast.