There is no much gain of using coroutines with blocking API. Coroutines are designed to simplify the use of
asynchronous (non-blocking APIs). Blocking APIs are already easy-to-use w/o any coroutines. However, async APIs are a pain to use w/o coroutines, and that is where they help. However, if you want consistency (make all your code coroutine-based), then you shall configure your coroutines thread pool in the same way as before (
CommonPool
is not appropriate for doing blocking stuff)