Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have read that select and multi-threaded programming were low performing IO models, for example this IBM developerworks article on high perfomance IO.
I do not understand how synchronising/aynchronising : Blocking/Non-Blocking is improving the performance. Why is AIO the best option here?
Being asynchronous and/or non-blocking does not provide any inherent speed boost to individual IO operations within a system, if it is going to take x milliseconds to read from the disk that’s what it will take.
The advantage of these approaches shows true in multi-threaded environments (or environments where operation can continue despite delayed IO) by allowing the IO operations to be effectively separately from the main thread of execution. The perceived performance increase from this is due to the decreased number resources used to simply wait for IO to return or unblock.
A good comparison of asynchronous and non-blocking is available in this thread.