Announcements

23283 readers

16 users here now

Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.

You can also find major news on join-lemmy.org

founded 5 years ago

MODERATORS

[email protected]

1446

We're the creators of Lemmy, Ask Us Anything. Starts Monday, 7 Aug, 1500 CEST (lemmy.ml)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

708 comments fedilink hide all child comments

This is an opportunity for any users, server admins, or interested third parties to ask anything they'd like to @[email protected] and I about Lemmy. This includes its development and future, as well as wider issues relevant to the social media landscape today.

Note: This will be the thread tmrw, so you can use this thread to ask and vote on questions beforehand.

Original Announcement thread

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

[–] [email protected] 9 points 1 year ago (3 children)

Is there any limitations with the database (postgres)?. I know postgres is one of the best (maybe even best) monolith database (running on one node) at the moment, but will the space be enough? With this in mind, has there been any consideration of migrating to a distributed database like ScyllaDB or CassanraDB to alleviate potential space constraints? On the other hand, if Lemmy doesn't intend to store data for long periods, maybe the capacity of Postgres would suffice. Any thoughts or plans on this? I appreciate your insights on this matter.

[–] [email protected] 15 points 1 year ago (1 children)

Disk space is definitely not an issue for us w/ postgres, or any text data really. The entire wikipedia english text data, is ~20GB. Images are the main disk-space concern for servers.

A backup of lemmy.ml's DB is only ~1.8 GB currently, and that's 3+ years of data.

We have no plans to move away from postgres, and lose all of its features and performance.

load more comments (1 replies)