Hacker News Reader

It has io and CPU schedulers which solved this issue around 5 years ago.

The asynchronous io API has nothing to do with this.

When I do bluray rips I run it with nice and ionice, works great. Been so long however, can’t remember if still necessary.

What about asynchronous I/O calls? Or using separate threads for I/O vs UI?

>What about asynchronous I/O calls?

>Or using separate threads for I/O vs UI?

not the target use for completion ports, which is handling thousands of outstanding IO requests with a few threads.

You mean an IO scheduler, eventually with a plugable architecture ?

epoll