Lemmy.world has been down between 02:00 UTC and 05:45 UTC. This was caused by the database spiking to 100% cpu (all 32 cores/64 threads!) due to inefficient queries been fired to the db very often.
I’ve collected the logs and we’ll be checking how to prevent this. (And what caused this)
lemmy.world is a test environment for Lemmy developers… 😅 Jokes aside, issue is an issue.
It’s a good reminder that other large instances (lemm.ee, sh.itjust.works, reddthat.com, sopuli.xyz) usually offer higher uptime while showing the same content as LW
My issue with the smaller instances is that I enjoy browsing Local, and this is typically not as active or interesting on there. Is there a way to browse lemmy.world’s Local from another instance?
Local makes sense for a country or field focused instance (queer rights, programming, even porn or whatever), not so much for generalist instances, unfortunately.
The way you use local only makes sense now as most of the communities are on LW. Once a few of them start to branch out (such as lemdro.id or startrek.website), if you want to see that content, you will either subscribe or use all
Every Lemmy update:
“We fixed some performance issues by optimising some queries.”
Also: “To balance it out, we added some new even more inefficient queries.”
How else are they supposed to patch things out? can’t leave it up to fate, gotta make your own destiny!
Thank you for the update!
(And what caused this)
Prediction: bad database programming. ;)
Are we extracting enough value out of our volunteer developers and DBAs?!
Thanks for keeping us updated. FYI i noticed an issue there was an error message saying to check (the matix) and (somewhere else, Lemmy community support?). Both of them pointed to the same URL, but im sure they were meant to point to different places.
Edit. Happed again and I took notes. Both point to lemmy.ml community support
