sh.itjust.works Main Community

7705 readers

4 users here now

Home of the sh.itjust.works instance.

founded 1 year ago

MODERATORS

TheDude@sh.itjust.works

manifex@sh.itjust.works

biela@sh.itjust.works

imaqtpie@sh.itjust.works

196

June 12 - Server Capacity Update (sh.itjust.works)

submitted 1 year ago* (last edited 1 year ago) by TheDude@sh.itjust.works to c/main@sh.itjust.works

84 comments fedilink hide all child comments

I'm aware that some of you have been getting some errors loading this instance. This was a configuration that I needed to be adjusted which has since been.

Do be patient if we run into other issues, I'll be continuously working in the back-end with others to better your overall experience.

Still a lot of capacity available!

edit: For those that are interested in the configuring changes. I was using the default lemmy configuration for the nginx worker_connections value. This value needed to be raised. Shout out to @ruud@lemmy.world over at lemmy.world for helping me out.

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

[–] PCChipsM922U@sh.itjust.works 3 points 1 year ago* (last edited 1 year ago)

As someone who is still hosting a forum, I would not suggest this. I have also tried to reduce footprint of the forum using external image hodting services and this has always ended up badly (images get lost as one hosting service changes policy and maybe disables direct linking or just closes it's doors, whatever).

This is one of the reasons why I'm not tempted to open up a lemmy server, even though my hosting plan allows 3 subdomains. Used space will rise quickly, even if it's just images... if videos are allowed as well, than all hell will break loose, even if they are processed and reduced in quality and resolution server side. I've seen it happen before, it's a nightmare to revert things afterwards (users complain), not to mention you can't revert the damage, that space is taken and that's that.

My estimate is that, if only images are allowed and images are processed in webp, it'll take about a week for a quite busy instance to reach the 1GB mark... probably a lot faster if it's an NSFW instance (a few days). Think about this from a migration perspective after 1 year - it will be a nightmare.