Originally posted by RomuloP
View Post
If there is no completion packet queued, the function waits for a pending I/O operation associated with the completion port to complete.
EDIT: They can call it a priority scheduler all they want, but the real truth is, all it does is issue slices of time or refuse to issue slices of time and that's literally it. The end result is constant serial streams of context switches. It's possible to actually see it with a profiler, seriously check it out. If all you want is a visual representation, then the easiest bet is to benchmark an IO bound linux app on both Linux and WSL and compare the bar graphs.
Comment