If a thread performs a blocking operation, the operating system will deprive it of the remaining unused time slice and let other threads start execution. Each thread will be allocated a certain amount of CPU time, during which the thread can run, and then another thread will be allocated a time slice and start execution. Ideally, the number of threads is equal to the number of processors, but this also requires that any thread should not perform blocking operations such as synchronized reading and writing, waiting for event notifications, etc., to avoid thread blocking. The number of threads depends on the specific needs of the application. Under normal circumstances, we will create a certain number of worker threads in the application to handle these notifications. After the socket is created, it can be associated with a completion port at any time. When an I/O operation is completed, a worker thread that can process the result of the operation will receive a notification.
#Windows afd socket buffer size windows#
On Windows NT and Windows 2000, the overlapped I/O mechanism of the completion port can really expand the response scale of the system.Ī completion port is actually a notification queue, and the operating system puts notifications of completed overlapping I/O requests into it. The completion port mechanism is optimized within the operating system. However, functions like WSAAsyncSelect() on Windows 3.1 and select() on Unix are easy to use, but they cannot meet the needs of response scale. This mechanism is particularly useful for those time-consuming operations. After the overlapping operation is completed, the thread receives the relevant notification. The overlapping operation request is completed in the background, and the operating thread is requested to do other things at the same time. Through Win32's overlapping I/O mechanism, an application can request an I/O operation. Of course, many of the points apply to both sides of the model. The main focus of the article is on the server side of the client/server model.
#Windows afd socket buffer size how to#
This article will discuss how to develop Winsock applications with high scalability on Windows NT and Windows 2000 through Winsock2. The real difficulty is to write a network application that can accommodate as few as one, as many as thousands of connections. Create and connect a socket, try to connect, and then send and receive data. Usually it is not easy to develop network applications, but in fact, you only need to master a few key principles.
0 kommentar(er)
