The async runtime is almost always built on top of non-blocking I/O APIs, and th... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

KMag on Feb 22, 2023 | parent | context | favorite | on: C++ Coroutines

The async runtime is almost always built on top of non-blocking I/O APIs, and the extra layer of abstraction adds overhead. You're rarely calling epoll in your async code, but rather your runtime is handling all of that for you.

That is, unless you're using io_uring, POSIX AIO, etc., in which case your async code might not have the extra layer of abstraction on top of the system APIs.

junon on Feb 23, 2023 [–]

io_uring isn't typically used directly, you're most likely using liburing which is already an abstraction. I don't really see your point.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact