we accidentally did the upgrade just now, which is what you just experienced. anyways we’re at like double the power and processing, and three times the storage we were previously at so yeah hopefully that’ll be good. anyways i guess i’ll leave this post stickied until i go to sleep in like an hour
oh god hopefully not with what we’re running now lol, we’ll see on the 12th i guess but for some perspective we can probably handle traffic of three to five times the intensity of what we did today (eyeballing it) based on just the metrics i can quickly reference now (i am not our tech person)
With r/spez’s AMA going the way it did I wouldn’t be surprised
If the Reddit admins weren’t deleting every post and comment about Lemmy, possibly there would be an influx.
there actually was a mass influx and there still is
Holy shit that’s almost a 90deg angle lmao!
Maybe admins should set up one of these donations pages with current donations for the month/monthly operational costs, so we can help when the maintenance budget gets a bit tight? I can help build that, if need be.
Here is a place you can contribute directly to the Beehaw instace.
It’s linked in the sidebar.
Where is this from, please?
https://the-federation.info/node/details/25274 here ya go mate
Thank you mate
I don’t know what that other link posted is, which I got warning for when I tried to visit, but I believe Beehaw primarily uses OpenCollective, and this is overview: https://opencollective.com/beehaw
Would it be worth adding a CDN (eg cloudflare or fastly) as a preventative measure? I don’t know what your traffic distribution is between static and dynamic content, but i imagine being able to offload image GETs would at least prevent you from getting surprise egress traffic bills.
CF also has an “always online” feature to serve a cached version of the site of the server is down. It won’t allow people to post it comment, but it might provide a smoother user experience.