lemmy.ml is overloaded, use other instances instead
lemmy.ml is overloaded, use other instances instead
This site is currently struggling to handle the amount of new users. I have already upgraded the server, but it will go down regardless if half of Reddit tries to join.
However Lemmy is federated software, meaning you can interact seamlessly with communities on other instances like beehaw.org or lemmy.one. The documentation explains in more detail how this works. Use the instance list to find one where you can register. Then use the Community Browser to find interesting communities. Paste the community url into the search field to follow it.
You can help other Reddit refugees by inviting them to the same Lemmy instance where you joined. This way we can spread the load across many different servers. And users with similar interests will end up together on the same instances. Others on the same instance can also automatically see posts from all the communities that you follow.
Edit: If you moderate a large subreddit, do not link your users directly to lemmy.ml in your announcements. That way the server will only go down sooner.
You're viewing a single thread.
@ devs:
Can you please focus your work on optimising performance for the UI? It will greatly reduce the amount of electricity and money spent, so you're actually multiplying every tenth of a second you can shave off of CPU time...
Thank you a lot for writing this software. It's been a great little project so far and it seems to go down the Mastodon route of increased popularity. Be proud!
We're about 80% done with a big rework of the UI to switch from websockets to http. This should solve most of the stability and performance issues of both the front and back end.
Huh, I thought websockets are far more efficient that http.
The sends might be... but keeping rooms of hundreds of active users open, much more difficult.
Yes I would have thought too, also I am seeing comments about high-cpu count VM but the bottleneck shouldn't be CPU per say. Maybe the database? Or code related issues, I see the back-end is written in Rust so it's not an inefficient language problem.
I am wondering if this is also the case a thousand of redundant requests that would need a clever caching system. Such system are fine in theory but quiet a task to implement.
Damn I am veeery excited!! Do you have an ETA? No pressure though :)
It's our top priority rn.
Great to hear, thank you for the update!
No probs!
lemmy devs are the best in the business hands down 💪