> > Well, but from operating system perspective, is Windows kernel capable > to accommodate and handle those many connections > (Considering factors like resource allocations in kernel per > connection)? Or do we need to tweak something in there? > > One opinion is that default WinSock cannot handle huge number of > connections and we need install a custom socket stack that supports that > many connections, but I am not sure about it. >
Not a Windows internals expert, but what you ask is nowhere related to libuv. Iff there is a limitation in the Windows kernel you would suffer it even if you use IOCP and Windows sockets manually. There is no limitation in libuv itself (if that's what you asked), it's all up to the OS. AFAIK, Windows has a limit of 2^24 handles per process (http://msdn.microsoft.com/en-us/library/windows/desktop/ms724485%28v=vs.85%29.aspx), so if there is a limitation, it might on Winsock2, but I have no ides. You might be able to find some answers on that leaked Windows 2000 source code though :-) Cheers, -- Saúl Ibarra Corretgé bettercallsaghul.com
signature.asc
Description: OpenPGP digital signature
