Asynchronous I/O is better in quite a few ways than the thread-per-client model. Optimal performance is actually achieve by thread-per-core, with each thread doing asynchronous I/O.
Note that your concept of "multithreaded server", while not exactly wrong, is quite different from what everyone else uses that phrase to mean. Generally it means one thread per connection and not the response to one connection parallelized across threads.
The example you're asking for is just a combination of single-threading synchronous server + parallel computation.