does wrapping blocking calls `withContext(<http://Dispatchers.IO|Dispatchers.IO>)` stop my threads ...

# coroutines

[asad.awadia]

does wrapping blocking calls withContext(<http://Dispatchers.IO|Dispatchers.IO>) stop my threads from getting 'blocked'?

[streetsofboston]

No. It does not prevent threads from getting blocked. It does prevent the calling thread from being blocked (instead, the calling thread will be suspended)
The Dispatchers.IO dispatcher, however, is designed to handle blocking threads (its pool is large and tailored for running code that may get blocked (often) - and do nothing but wait)

[asad.awadia]

I thought it had only 64 threads

[louiscad]

ONLY? 64 threads is a lot! You can still change it though.

[louiscad]

That's the upper bound BTW, it won't create 64 threads if you only need 13.

[asad.awadia]

Maybe client side 64 is a lot

[asad.awadia]

I m looking at it from server side

[louiscad]

On server side, you should use non blocking I/O whenever possible so you don't need <http://Dispatchers.IO|Dispatchers.IO> unless really needed for filesystem I/O.