/kbin meta

5 readers

6 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

Last few days are the least functional kbin has been for me since the July exodus. Just me? (kbin.social)

submitted 10 months ago by be_excellent_to_each_other@kbin.social to c/kbinMeta@kbin.social

26 comments fedilink hide all child comments

Just curious if it's somehow got to do with anything on my end. I'm generally desktop-only, firefox-only.

you are viewing a single comment's thread
view the rest of the comments

[–] Gordon_Freeman@kbin.social 6 points 10 months ago (1 children)

Kbin is not lemmy

[–] originalucifer@moist.catsweat.com 7 points 10 months ago (1 children)

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.

[–] stevecrox@kbin.social 1 points 10 months ago (1 children)

When I looked at Kbin the "caddy" was wrapped around RabbitMQ. You can get RabbitMQ to solve a lot of those issues.

Firstly with Rabbit you can set a Time To Live header in messages.

By default RabbitMQ queues have no limit in size, you can set a limit.

Lastly RabbitMQ allows message prioritisation. So you can drop the priority of things the older/more retries they contain.

Most of this is either RabbitMQ policy or Queue rules based on Headers in the AMQP message. Depending on how KBin is generating messages you might be able to do this as a system admin

[–] originalucifer@moist.catsweat.com 1 points 10 months ago

oh yep, am familiar with the underlying tech. the mbin devs had this resolved relatively quickly.