To develop a scalable service on NT you have two choices. One kernel thread per each user connection, or use IO completion ports.
One kernel thread per user connection does not scale well due to excessive thread context switching by the kernel
Other way around is to use IO completion port. Here you have one active thread per cpu. Each thread handle multiple connections with asynchronous IO - a real pain in the ass.
Solaris supports both kernel mode and user mode threads and is definitely superior for a scalable easy to code synchronous solution.
Slashdot Mirror
To develop a scalable service on NT you have two choices. One kernel thread per each user connection, or use IO completion ports.
One kernel thread per user connection does not scale well due to excessive thread context switching by the kernel
Other way around is to use IO completion port. Here you have one active thread per cpu. Each thread handle multiple connections with asynchronous IO - a real pain in the ass.
Solaris supports both kernel mode and user mode threads and is definitely superior for a scalable easy to code synchronous solution.