TendieMaster69@sh.itjust.works to sh.itjust.works Main Community@sh.itjust.worksEnglish · 1 year ago
- cross-posted to:
- chat@beehaw.org
TendieMaster69@sh.itjust.works to sh.itjust.works Main Community@sh.itjust.worksEnglish · 1 year ago
- cross-posted to:
- chat@beehaw.org
Anyone know why? Any way we can promote sh.itjust.works to lighten their load possibly?
You must log in or register to comment.
Only way to do that is have redditors understand that they don’t need to be on the most popular instance in order to have a great experience.
In other words, nothing we can do, it’s gonna take a while :)
Hey I’m a redditor and I’ve gone as far as setup my own instance rather than register on the “big ones”.
Just being a bit snarky, don’t mind me :P
It’s all good. No offense taken. I appreciated your comment.
The sad thing is, many will lose hope and divert to twitter or gab or something and say F lemmy and the fediverse all together
Very likely that a lot will, but this isn’t a big VC-funded thing where we measure success by growth and profit. If we have enough users to maintain a lively and interesting community and can slowly grow after that, still a win for us.
True, i agree with your assessment
i think in future perhaps instance owners would have a temp place holder page; stating that the instance is down - please select an alternative from the list below. that way at least people get some idea of what’s going on and how to move forward from it.
The lemmy_server code is not scaling well, lots of database contention.
Supposedly they are working on major performance improvements for the next release. No idea when it is scheduled to come out though.
The database stuff was solved today. The bigger job, happening as we speak and hopefully finishing in a week or two, is ripping out all the WebSocket stuff and replacing it with simple HTTP. No more crazy updating feeds and weird buggy vote numbers, on top of the performance stuff.
That’s great news! Is there a new release candidate with the DB changes?
What was it? Missing indexes? Bad query plans? Bad queries in general?
Glad to see websockets getting ripped out.
The hot_rank query was basically hitting the server like a truck. You can read more about it in this github issue, but basically calculating the hot rank in the database has been moved to rust.
EDIT: For clarity, the database issue was solved a bit ago, but today it was released as a Lemmy version which this server (sh.itjust.works) is now on.
Excellent! Time to upgrade my instance!
- BE 0.17.4
- UI 0.17.4
Upgrade complete! Thanks for the info. BTW, the new UI version no longer shows the UI version in the page footer.
deleted by creator