195

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

[-] TheDude@sh.itjust.works 14 points 1 year ago

I figured out the storage issue last night, the instance is only at about 20% utilization so we should be good to take on a good amount more. We probably will need to do some more tweaking as we grow but for now its looking pretty good!

[-] VinS@sh.itjust.works 7 points 1 year ago

In Montreal, do we need to send you some hard drives?

[-] Barbarian@sh.itjust.works 2 points 1 year ago

Wow. 20% usage at 2.4k users is pretty damn amazing.

[-] TheDude@sh.itjust.works 10 points 1 year ago

its not so much about how many registered users as it is about how many online users. The online user count is what adds fuel to the fire!

[-] flambonkscious@sh.itjust.works 4 points 1 year ago

Oh wow so it's really the transactions per minute, not so much the baseline set of data?

[-] PCChipsM922U@sh.itjust.works 1 points 1 year ago

Yeah, basically the problem is number of calls (requests) per minute. If it's not too many, everything works fine, if it overloads, you get 500 errors 🤷.

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

Including calls to federated communities, yes?

[-] PCChipsM922U@sh.itjust.works 2 points 1 year ago

I'm not sure about that, but most probably yes, since if you post on federated communities, your username pops up as someone@notonthisserver.com and the post is saved on your instance (from what I know).

[-] imaqtpie@sh.itjust.works 1 points 1 year ago

Good to know. Keep up the good work, you're the man.

[-] PCChipsM922U@sh.itjust.works 1 points 1 year ago

Think long term. Don't take too many new users or you'll end up with loads of new content (mainly images). Storage is not expensive nowadays, but you can't load new disks to the arrays indefinitely.

[-] can@sh.itjust.works 3 points 1 year ago

Can't we just link to images hosted elsewhere? Like a certain site I once knew

[-] PCChipsM922U@sh.itjust.works 2 points 1 year ago

We can, but then you might loose history. This is long known problem on forums. Trying to cut on disk space by linking to image hosts. Sometimes the images survive, most of the time they don't. If that doesn't bother most of the user base, fine, but certain communities would like to keep a history of the media, since sometimes they share valuabe information, like maybe schematics or art.

[-] can@sh.itjust.works 2 points 1 year ago

I guess it's a balance. I remember the imageshack purge but I also don't want to overload the instance.

[-] PCChipsM922U@sh.itjust.works 1 points 1 year ago

Photobucket was next after that, not to mention countless others. Imgur has been pretty consistent over the years, but after 2 purges and hundreds of lost images (schematics in most cases) on my forum, I'm scared to death of trusting another image hosting company.

Basically, we still allow externally hosted images on the forum, but only for temp things, like buy/sell, stuff like that. Everything else is attached on the forum.