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.
You must log in or register to comment.
Yeahhhhh you don’t want to store images in a database. That will kill the database in a hurry. Store references to object storage.
It’s ironic cause object storage for pictrs is a relatively new feature
MSSQL has had blob storage for a while and I don’t know anyone that uses it. Their Filestream stuff was interesting by letting you store it in the FS but be indexes via the DB, but come-on, use a damn pointer people.
My company stores some 80+ TB in a series of MSSQL databases. Yes, you read that right. In. Each DB is allowed to grow to 250GB, then a new one is created and written to while the old one becomes read only.
That is horrific. In my day job, I stored images in a database in my first job, learnt my lesson and now have an allergic reaction just thinking about it.
Thanks for your hard work by the way.
That 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.
You haven’t clarified yet as to whether or not you were storing the actual image data in the database…
That’s how Lemmy does so by default. I wish I was kidding 🙃
I’m not sure how it still surprises me that someone could be THAT stupid. Yes it’s called a "data"base, but it’s for storing meta data, and short text data, not images/video/PDFs. Fucking carpenters always using a hammer for any job and plumber using a crescent as a hammer. Insane.
Lemmy uses pict-rs for image storage, which can store on the filesystem or object storage (filesystem is the default) and Lemmy’s default config doesn’t seem to change that
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.
The 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.
One 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.
I completely agree.
The models retire, the photographer or rigger retire, or shut down because of piracy.
Torrents and download links disappearing.
Fuck pornhub for multiple reasons.
It’s such a shame.
Support the artists while you can, because that’s what they are, and preserve their works for posterity.
Yeah that was such a heartbreak, like over half the website just disappeared over false allegations and so much really popular amateur content gone forever was deleted for no reason in the purge.
It 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.
You underestimate the average porn addict. People were downloading years of porn they’d ‘saved’ on Reddit while making their escape.
The save option is still there.
Also, This lemmy instance is actually more likely to fail right now than most of these established image sharing sites.
I did that. I have like 5 comics from when imgur started deleting porn.
The only real solution is to pay to host images. Nobody will accept though so we end up with the issues you describe.
deleted by creator
deleted by creator
Distribute the load!
Who pays for Catbox?
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.
Welcome to Lemmy.
I am using object storage on my personal instance, migration should also be relatively simple, pictrs has good documentation.
They do not. They just didn’t phrase it right
Other comments seems to suggest otherwise.
I am literally hosting one of the biggest lemmy instances and I’ve been where they are before.I know what I’m talking about
Then educate us instead of boasting and being negative…
Sharing knowledge > sharing opinions
Lemmy uses pict-rs for image storage, which can store on the filesystem or object storage (filesystem is the default).
Lemmy’s default config
Removed by mod
Bad idea having the photos and content stored in your paostgres DB. Better on a separate product like HCP or some other object storage platform
Do what needs to be done, boss! We’ll be here waiting for you.
Hey, you do what you gotta do.
Thank you.
Oooh neat! Which object storage are you guys using? Ceph? MinIO? Something else? Would love to discuss gory details!
deleted by creator
I 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)?
By 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
It would be interesting if hosting images via IPFS was an option, but that would require pretty heavy changes on Lemmy’s side.
Removed by mod
Note if you’re migrating pictrs you don’t need a whole lemmy downtime. Just pictrs
Thx I’ll try to do that way.
Also it will be way more time than you think. The migration is slooooooow.
25GB in 4 hours. Looks like it will take a few days 😕 I asked it to the Matrix chat, hopefully they have a solution.
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!
You 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.
deleted by creator
