It's run by the people that are making Lemmy. They're very busy improving the code, which we already benefit from on our server, but I understand they don't also have the time to update lemmy.ml with every change in code. I think a lot will improve as soon as 0.18.1 is released and am sure they will update lemmy.ml as well.
Usually no. The problem is, that lemmy.ml is hosted on a too underpowered server or has a too slow data connection to handle the amount of users. In the last 2-3 weeks user count skyrocketed due to Reddit fuckups.
Instances with servers capable of handling the amount of users/requests will run better.
Instead of pointing users directly to lemmy.ml it would help mentioning https://join-lemmy.org/ instead so the load spreads over multiple instances. Also disabling registration on here might help in long-term.
So, everyone: Advertise Lemmy! But don't advertise lemmy.ml! 😀
it's running the 0.18.0 version which has some SQL problems that were fixed in recent 0.18.1 rc's
(unless the devs here are using a custom build)
Speaking of, I wonder if there is a way to specify Ansible to use the latest RC
@authed It's a pretty new app so it's about as reliable as the early Reddit days. It will improve over time.
It's not due to poor hardware resources. The problem is due to low backend performances. I don't know if lemmy.ml is updated but the new patch will implement a lot of performance tweaks. For example, lemmy.world's admins found many huge performance issues and they made a couple of PR that have been merged so they will be available in the next release.
So just I come to this post I notice things are working much more snappily! They’ve just updated the server it seems! Much better right now.
Yeah I noticed this also... Today it is much faster... Might be the update to 0.18.1 that did it
Oh it is for sure. Still it’s prob a beta test of 18.1.
I wasn’t even able to register on this instance and I still get long “pending subscription “ times.
Most instances I’ve come across have enough resources relative to usage.
It can be on instances with lots of users and open signups.
Slow, no, but there’s definitely some bugs and weird little quirks. We’re not even at a version 1 release yet.
It's run by the people that are making Lemmy. They're very busy improving the code, which we already benefit from on our server, but I understand they don't also have the time to update lemmy.ml with every change in code. I think a lot will improve as soon as 0.18.1 is released and am sure they will update lemmy.ml as well.
Usually no. The problem is, that lemmy.ml is hosted on a too underpowered server or has a too slow data connection to handle the amount of users. In the last 2-3 weeks user count skyrocketed due to Reddit fuckups.
Instances with servers capable of handling the amount of users/requests will run better.
Instead of pointing users directly to lemmy.ml it would help mentioning https://join-lemmy.org/ instead so the load spreads over multiple instances. Also disabling registration on here might help in long-term.
So, everyone: Advertise Lemmy! But don't advertise lemmy.ml! 😀
it's running the 0.18.0 version which has some SQL problems that were fixed in recent 0.18.1 rc's
(unless the devs here are using a custom build)
Speaking of, I wonder if there is a way to specify Ansible to use the latest RC
@authed It's a pretty new app so it's about as reliable as the early Reddit days. It will improve over time.
It's not due to poor hardware resources. The problem is due to low backend performances. I don't know if lemmy.ml is updated but the new patch will implement a lot of performance tweaks. For example, lemmy.world's admins found many huge performance issues and they made a couple of PR that have been merged so they will be available in the next release.
So just I come to this post I notice things are working much more snappily! They’ve just updated the server it seems! Much better right now.
Yeah I noticed this also... Today it is much faster... Might be the update to 0.18.1 that did it
Oh it is for sure. Still it’s prob a beta test of 18.1.
I wasn’t even able to register on this instance and I still get long “pending subscription “ times.
Most instances I’ve come across have enough resources relative to usage.
It can be on instances with lots of users and open signups.
Slow, no, but there’s definitely some bugs and weird little quirks. We’re not even at a version 1 release yet.