> "which in case of evented framework will be heavily underutilized."

I'm not following your logic here. If something doesn't need 16 CPUs, why is splitting it over 16 cores a good idea? You're going to be adding a lot of inefficiency, complexity etc for no gain.

Most of mine are dual or possibly 4 core.

One core for OS stuff, other processes etc, one core to do networking IO for me.

As I say, networking IO shouldn't be using CPU. If you're doing long or blocking jobs, pass it over to some other thread. (That's a far better way to utilize multiple cores than splitting the whole networking IO over multiple cores).