About our recent downtime, and likely upcoming downtime.
About our recent downtime, and likely upcoming downtime.
Hey yall, just wanted to chime in with a quick update on why we were down and have gone down a few times these past few days.
So... for those who don't know a bit on the backend way of how lemmy works right now, it's a lil more than a mess. Lemmy itself uses very little computing resources, you could probably run a decent instance on a toaster (I wouldn't suggest it though) but the problem that arises rapidly is the way photos are managed. The photo database downloads images both that are uploaded and federated. There is an option to disable caching for federated NSFW posts by unchecking enable NSFW within the instance admin panel. That's the only option related disabling federated images as of right now.
You see where I'm going with this, with this instance being as large as it is? Our photo database has been filling up pretty rapidly. We are attempting to troubleshoot solutions to prevent caching all federated content. Unfortunately as our backend team is attempting to figure that out, our pictures database just keeps ballooning more and more.
We have deleted some stuff in hopes to give more time, but we unfortunately have no choice but to migrate to object storage ASAP. Tomorrow there will likely be downtime as we migrate things over, and unfortunately there is no telling how long that will take.
Thank you for being patient and understanding while we navigate this. If you want to see updates to our status when we go down, check out our mastodon page here or come to our matrix public operations channel for updates (link in the sidebar.)
Things should work today though. Emphasis on should.
We are working on open collective still, but hosting this instance does cost money. If you are able to, donations are greatly appreciated. Especially as we will have to factor in object storage into our costs now.
Yeahhhhh you don’t want to store images in a database. That will kill the database in a hurry. Store references to object storage.
64It's ironic cause object storage for pictrs is a relatively new feature
41Thanks for your hard work by the way.
8That is interesting. Oh well, I’ve met developers who didn’t always make the best design decisions for the backend until their ass has had chunks removed.
6
Just remove direct uploaded pictures, there are a number of image hosting sites that already exist that are both setup for this kind of thing and that people already use and link to.
This is already the case for videos for the very same reason.
30The problem with a 3rd party hosting site is that there's no guarantee they suddenly won't go out of business, or hide or delete all their nsfw content like imgur and Tumblr and many others in the past.
Just hosting images for another site like this one isn't profitable because they can't sell ads for the hotlinked images served to users of that other site.
It is a conundrum to find a working long term solution.
35One of the worst things when it comes to porn is videos or pictures being deleted. Especially frustrating to browse old forums and none of the download links work or none of the images show. Or when pornhub deleted nearly 80% of their videos. There are videos out there which I am still looking for. Probably will never find again. Partly the reason I am a hoarder.
16It really isn't a problem when we're talking about these kinds of images. This isn't a type of content that if it disappears in 12 months anybody is going to feel great loss for. It's not instructions on how to maintain some esoteric computer system, or some sort of critical cultural records. It's a transient commodity, with a steady stream being generated all the time. Nobody is going back and browsing the stuff that was posted 5 years ago.
Anyone who wants to keep such images for extended periods is able to save them locally to their computer as they get posted.
11The only real solution is to pay to host images. Nobody will accept though so we end up with the issues you describe.
4Permanently Deleted
1
Permanently Deleted
16Distribute the load!
6Who pays for Catbox?
2
Please tell me you're not putting the images actually /IN/ the database? Images/files don't belong in the fucking database(we have had customers try to do this and it's the biggest headache to get fixed). You only put LINKS to files in the database.
14Do what needs to be done, boss! We'll be here waiting for you.
9What benefit does object storage have over right now?
9Bad idea having the photos and content stored in your paostgres DB. Better on a separate product like HCP or some other object storage platform
12
Oooh neat! Which object storage are you guys using? Ceph? MinIO? Something else? Would love to discuss gory details!
8Hey, you do what you gotta do.
Thank you.
8I can't believe you're only just moving to object storage! Offload that stuff as much as possible (this is probably a grandmother suck eggs situation, I know).
When you say "photo database", do you mean Lemmy literally stores the binary image files in the db, or just the storage area for images (ofc linked to from the db)?
7By default lemmy as a software, the whole photo database is stored directly into a file folder that links itself to the drive. The entire photos. And of course the drive just rapidly inflates like a balloon since it stores not just local images but federated images
6
Permanently Deleted
6It would be interesting if hosting images via IPFS was an option, but that would require pretty heavy changes on Lemmy's side.
6Who do you think plans on paying for that?
2
Thanks for the update and the openness. Hope you are able to make it work with a minimum of fuss, and that all the users understand. Good luck!
5You might want to look at storj.io for object storage. We've been using it in production at work and are really satisfied. It's priced pretty well, highly available, high throughput, multi regional by default and s3 compatible.
5Permanently Deleted
2