June 12 - Server Capacity Update

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 over at lemmy.world for helping me out.

oxideSeven,
@oxideSeven@sh.itjust.works avatar

my all/hot on here hasn't updated in update 10 hours. Is that something with our instance?

Checked on a different instance and it seems to work fine.

csm10495,
@csm10495@sh.itjust.works avatar

Same here.

Whooping_Seal,
@Whooping_Seal@sh.itjust.works avatar

Just out of curiosity, would it help if when posting images we use services such as imgur (or alternatives)? I’m assuming if there is storage issues those type of posts are the biggest culprit.

Thank you for hosting this server @TheDude :)

player1,

Funny enough I’d say Shit Doesn’t Just Work - it takes your hard work. Thanks for helping fill the Reddit void @TheDude

can,

Are things scaling well then? Is it still alright to recommend new people come here or would you rather hold off for a bit now?

TheDude,

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!

PCChipsM922U,
@PCChipsM922U@sh.itjust.works avatar

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,

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

PCChipsM922U,
@PCChipsM922U@sh.itjust.works avatar

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,

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

PCChipsM922U,
@PCChipsM922U@sh.itjust.works avatar

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.

can,

Imgur is deleting all images that were uploaded without being signed into an account.

PCChipsM922U,
@PCChipsM922U@sh.itjust.works avatar

Didn't know that, thanks for the info.

can,

And all nsfw too iirc

manifex,

Thanks @TheDude! Scaling systems like this is always a challenge and you really get to learn the performance quirks of the code. Thanks for all your work.

scarrexx,

Thanks for the fix @TheDude.

falkerie71,
@falkerie71@sh.itjust.works avatar

Thanks for the update! Any plans for a separate channel outside of sh.itjust.works like Discord or Mastodon, just in case to give people a heads up if the server goes down or is in maintenance?

PolDelta,

I like the idea of a status account on Mastodon. That’s probably a little more accessible than Discord.

Echolot,

Would love to hear some more details on the misconfiguration if you want to share @TheDude

TheDude,

just updated the thread post to include more information for your curious beautiful mind

taladar,

Not sure if you already did or the default config does it but if you only have one backend in an nginx reverse proxy it might also make sense to configure the max_fails and possibly the fail_timeout options so nginx won't consider your backend down for a few seconds every time it receives a TCP error connecting to that (single) backend. max_fails=0 in the named upstream section (see http://nginx.org/en/docs/http/ngx_http_upstream_module.html#upstream ) is what you want here.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • main@sh.itjust.works
  • slotface
  • kavyap
  • thenastyranch
  • everett
  • tacticalgear
  • rosin
  • Durango
  • DreamBathrooms
  • mdbf
  • magazineikmin
  • InstantRegret
  • Youngstown
  • khanakhh
  • ethstaker
  • JUstTest
  • ngwrru68w68
  • cisconetworking
  • modclub
  • tester
  • osvaldo12
  • cubers
  • GTA5RPClips
  • normalnudes
  • Leos
  • provamag3
  • anitta
  • megavids
  • lostlight
  • All magazines