-
Notifications
You must be signed in to change notification settings - Fork 7
Don't store duplicate images #21
Comments
This will be nice. Sometimes I don't like the fact I have to backup 13GB of thumbnails. |
Bump! (of course that doesn't work here github) This would fix also that problem when picture if fully archived later, older ones haven't correct link. For example http://archive.rebeccablacktech.com/g/image/HZZG8IG0r6r7M4STnJBs-w >>22525926 goes to 404 |
This is related so I'll post it here: upscaled thumbnails look like crap, you may want to save both small/reply and large/OP thumbnails. |
They are. See woxxy's explanation on /foolz/. Sent from my Nokia phone |
What are you replying to?
Okay. |
I mean they do store both thumbnails, but since the old images aren't in place yet, ffuuka falls back to the reply thumb, if it was grabbed in the meanwhile. Sent from my Nokia phone |
I see I see. My high standards expected ENTREPRISE QUALITY migrations with 0 impact on the end-user. My bad. You should stop with these
It's really awkward. |
Yeah, everything about nokia is awkward at this point. Anyway, I'll most likely come up with easier methods to speed things up for image migration, once things return to me. |
Matching This and its variations. We ran it in batches so it doesn't rollback if it dies (and I believe it would also lock all the rows if we didn't):
/a/ is gigantic so we might be a special case, lucky we're "soon" done anyway. Other archive hosts might have less powerful servers so this might be a situation even for smaller boards. |
A quick check for /a/ shows that 66% of all images are reposts. It seems that one can considerably lower the disk space needed for thumbnail and full image archival by storing each unique image only once.
Requires dumper changes and possibly a rather heavy migration script, but it's feasible.
The text was updated successfully, but these errors were encountered: