For what it&#x27;s worth, the network I&#x2F;O model design+implementation is rarely what makes the difference between high performance, or not, &#x27;servers&#x27; -- and that is a mostly solved problem, at least in terms of patterns and practices that are adopted by &#x27;modern&#x27; servers (few threads, no more than actual hardware CPU cores, async.multiplexing, etc).<p>High performance is about everything else, including processing actual incoming requests efficiently, reducing block&#x2F;busy time in threads, caring a lot about memory access&#x2F;caches. They key IMO is concurrency and migrating blocking operations to other dedicated threads, and this is where an efficient coroutines implementation would help both with accomplishing that task, but, perhaps more importantly, keeping the programming model simple.<p>C++17 will introduce support for reusmable functions ( <a href="http:&#x2F;&#x2F;blogs.msdn.com&#x2F;b&#x2F;vcblog&#x2F;archive&#x2F;2014&#x2F;11&#x2F;12&#x2F;resumable-functions-in-c.aspx" rel="nofollow">http:&#x2F;&#x2F;blogs.msdn.com&#x2F;b&#x2F;vcblog&#x2F;archive&#x2F;2014&#x2F;11&#x2F;12&#x2F;resumable-...</a> ). This will be a game changer. Now, you can approximate this by e.g creating task abstractions and use lower-level(but slow) setjmp&#x2F;longjmp functions, or just design tasks&#x2F;functors that hold state that can schedule other tasks in turn, and so on. It works, but the overhead, mental, but also n terms of processing&#x2F;executing&#x2F;scheduling can be too great.