Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our July 2023 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
According to current system metrics, BeeHaw is running pretty dang well today. Might be the distance from our server to your eyeballs, or some other intermediate slowness.
We will keep trying to work on performance improvements where ever we can though. Still a work in progress.
Firstly
You are doing great work!!!!!!!!! I love this site!
Second of all makes sense, if you need help, don't be afraid to send me a message. I'm a rust developer and could help out if need be.
Thank you! I am not a rust developer, so staying away from the Lemmy codebase itself. However they always have open issues. I'm partial to seeing a few of them worked on more quickly, but can't complain about it.
It was a bit slow lately. But what I found really weird is that my feed wasn't being updated earlier today. Using 'hot' generally has posts from 1-2 hours ago and it was being shown posts from 4+ hours ago.
It's all back to normal now so it's all good.
Yeah I’m new to Lemmy. I tried signing up for Beehaw and idk if I ever got accepted.
signing up is fine, it just takes a bit to be accepted but replies feels slow
As a European, I've found beehaw snappy and responsive in the morning.
Between 14.00-16.00 it starts slowing down.
I've noticed this across a lot of instances as well.
I think it's just the surge of NA users
Maybe we need more servers up when NA happens?
Unfortunately, a Lemmy instance currently scales vertically.
To stop an instance from being overloaded, it needs more CPU/RAM on a single server.
Lemmy's horizontal scaling comes from more instances federating with eachother. Which is why there are a lot of comments and posts about "please pick a quiet instance".
I know people are trying to get a single instance to work across multiple servers, which would allow for load balancing and dynamic scaling.
However, at the scale Lemmy is currently operating at: throwing bigger hardware at it is easier than getting Lemmy to autoscale and use more hardware.
I imagine in a month or so, solutions will be developed to make horizontal scaling more accessible.
Do the protocols lemmy uses not allow for that?
The protocols Lemmy uses rely on additional instances and federation to scale horizontally.
That's kind of the point of the fediverse. There shouldn't be big instances.
The issue is a lot of users want to be on the busy instances.
Whilst it shouldn't matter which instance you actually join and use, some instances might have community/moderation that aligns with how you want to experience Lemmy (eg beehaw)
Lemmy hasn't been developed for a single instance to scale horizontally. Throwing bigger hardware at it is the correct way to implement scaling when a project is this size/maturity.
Having stateless middleware, running caches, sharding databases, database replication, read/write load balancing on databases, having the actual front end load balancers....
It's a difficult problem. Companies have entire teams that work on this, and it requires a lot of skill and attention to keep all the parts working correctly, and ensure things are fault tolerant.
Most instances are run by volunteers and community funding.
Like I said, hopefully Lemmy will move to a format that allows for easier scaling. But it's a lot of work.
There is probably more value in squashing bugs, improving user experience, adding some well-needed features, and any optimizations they find along the way - than there is in rebuilding the stack to support horizontal scaling.
Remember, Lemmy has a core team of 2 developers.
And this massive influx of users became apparent at the start of this month.
It's going to take some time, and things will be rough round the edges.