Lemmy

12524 readers

19 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

139

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

89 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

[–] teolan@lemmy.world 9 points 1 year ago (3 children)

The 700MB are the postgres data or everything including the images?

I'm under the impression that text should be very cheap to store inside postgres.

[–] cestvrai@lemm.ee 5 points 1 year ago (1 children)

Keep in mind that you are also storing metadata for the post (i.e. creation time), relations (i.e. which used posted) and an index.

Might not be much now but these things really add up over the years.

[–] teolan@lemmy.world 1 points 1 year ago

Yes but those are in general a couple of bytes at most. The average comment will be less than 1KB. Metadata that goes with it will be barely more.

On the other hand most images will be around 1MB, or 1000x times larger. Sure it depends on the type of instance but text should be a long way from filling a hard drive. From what I've seen on github the database size is actually mostly debugging information, so it might explain the weirdness.

[–] ubergeek77@lemmy.ubergeek77.chat 2 points 1 year ago

On average, 500MB is Postgres, 200MB is Pictrs thumbnails. Postgres is growing faster than Pictrs is.

[–] zoe_codez@lemmy.digital-alchemy.app 2 points 1 year ago

My local instance that I run for myself is about a week old. Has 2.5G in pictrs, 609M in postgres. One of those things that'll vary for every setup