Speed/Performance Characteristics of blocking vs Non-Blocking winsock?

Because it isn't about speed. The operations write and read are just memory copying in disguise. All they do is copy data to and from the kernel, respectively.

I.e. They don't actually send or receive anything .

In my experience non-blocking winsock operations are slightly slower but much more scalable. The fact is that you need to make two system calls plus some dispatching at the application level when you perform nonblocking I/O (with IOCP) and one system call if you use blocking I/O. If you have many concurrent connections, nonblocking I/O is much faster because of more scalable architecture if implemented well.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.