this post was submitted on 30 Dec 2023
30 points (100.0% liked)
/kbin meta
12 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What does any of this have to do with kbin? Kbin is not Lemmy. Completely different codebase.
the lemmy changes are causing excessive resource use on my 'bin instance. so yeah, not using lemmy, but being directly affected by the lemmy snafu.
my failed messaging queue is filling, which has its own retry logic.. that queue buildup also takes disk space.... extra processing, extra disk space.. this leads to 'worker' slowdown and then system failures and timeouts.
Oh, interesting. My bad then, it's common for people to be unaware that kbin is a different thing from Lemmy and so I made an incorrect assumption.
I suppose this reveals some room for improvement in kbin, then. Other servers' problems shouldn't be impacting kbin as badly as this, likely indicating that kbin needs to add some robustness when it comes to dealing with stuff like this.
your thought process isnt completely off. if my server product was detecting the failures correctly, these resources wouldnt pile up.
i dont think people really understand just how brand new all this stuff is. 'the fediverse' is under active development. they call it the 'bleed edge' of technology because its painful. most fediverse servers are experiencing growing pains of some sort.
the Lemmy/kbin sides are still wet behind the ears. i just hope people dont give up!
The beginning of reddit was much the same. Things stopped working all the time. Weird bugs popped up. And there were people posting posts like this a lot trying to figure out what was going on.