I understand your reasoning about the thread pools...

# ktor

[nomad]

I understand your reasoning about the thread pools @orangy - and unlimited is too much, if we aren't getting any requests finished we obviously shouldn't keep taking on more work, but on an 8 core machine Netty is restricted to 3 blocking threads, which seems very low in a world that is normally full of blocking i/o (db access) - to me it seems the numCores / 3 is optimized for entirely non blocking work, and but this seems near impossible for any website to actually obtain, so until some scheme to offload work waiting for i/o it seems to be me the only way to get around it is to increase the amount of threads in this pool? The problem we were seeing (we switched back to Jetty today after the deadlock was fixed), was that if we had 3 slow queries running, the entire server would stall, even if it was no where near its cpu limit, because it was just waiting for those 3 slow sql queries to finish executing.