You can see the details on user counts here: https://fedidb.org/network/instance/infosec.pub.
There are about 450 active accounts.
It’s hard to pin down the memory and CPU usage, as it’s running on a very large pair of AMD servers that host many sites. I posted the details of those servers are in the thread below. Prior to moving to this server, I was running the instance on a single 16 core AMD system with 64GB of ram.
Disk wise, it uses about 500GB. Overall, it is pretty efficient, particularly compared to kbin/mbin, however I think those are tough to compare against, since they have streaming updates and a heavier user interface.
My server bill is about $3000 per month, but that includes Infosec.exchange, which is a very large instance with about 17000 active users.
I don’t play around any more :)
ok - infosec.pub is now running on my main infrastructure - a 48 core/96 thread AMD epyc zen4 genoa with 256GB of DDR5 ECC ram and 2x4TB nvme SSDs, backed by a dedicated database server with the exact same specs, on a 10gbps network.
Hello - I will take a look. There isn’t an obvious problem
What site is the “loud extremists”?
I block instances that are the source of issues - shitjustworks caused a river of complaints - I don’t think I’ve seen any from the others.
I block them as they come up as problematic. There isn’t a handy list of instances to block like in mastodon. I will block those others.
Apologies for just seeing this. I have continued to chase down the causes of the error 500’s, which all appear to be related to a bug with how kbin is creating records for certain images in certain circumstances. I created some cron jobs that run every 15 minutes which fix the problems shortly after they develop. My hope is that I’ve resolved all of the error 500 issues as of this morning, though I’ve thought that before.
I appreciate the offer and will likely make a call for more help soon.
It’s 100x worse than Mastodon but 100x better than kbin (so far)
I will take a closer look, but I strongly suspect this is the result of overly aggressive filtering to avoid xss