Sorry for any site interruptions/instability last night into this morning (CST), but I ran into a bit of a problem with a recent Mbin update that was causing excessively high CPU usage with the message workers that is looking more and more like an upgrade that went rogue… or it’s the only explanation I have since everything is running fine after downgrading and performing the upgrade again.

However, I’ve since moved kbin.run to my primary self-hosted Proxmox host. The VM specs are listed on the FAQ page, but the bare metal host has a total of 128 GB of OC-ed DDR4 and a Samsung 980 Pro 2TB NVMe (with updated firmware)… plenty of room for activities now. This was a move I had planned to do in a few months, but figured I might as well do it now to exercise my backups and disaster recovery plan.

I also re-optimized PHP and Postgres for the new environment, so hopefully things are running as fast as possible with this VM configuration.

Enjoy!