[twsocket] TWSocket Stop Listening After Certain Numbers of Connected Clients.

2007-09-12 Thread Edward Koo
Hi Wilfried, thank you for replying. How do i check how much non pageable ram is available? The test i did for Windows Server 2003 runs on a system with Xeon processor and 3gb ram. It consistently stop at 180-200 concurrent clients which is very strange compared to the other test that accepts 500-

Re: [twsocket] TWSocket Stop Listening After Certain Numbers of Connected Clients.

2007-09-12 Thread Wilfried Mestdagh
Hello Edward, Possible you ran out of buffer space. Winsock use non pageble ram. The non pageable ram can grow to max 1/8 the size of total ram. Depending on traffic each socket need about 6 KB of it. And lots of other applications uses that part of RAM also (all overlapped IO for example). After

[twsocket] TWSocket Stop Listening After Certain Numbers of Connected Clients.

2007-09-11 Thread Edward Koo
Hi, I wrote a server with TWSocket that receive high speed data and then push the data to connected clients. I did some stress test recently and found that the server will stop accepting client after it reach something like 500-600 concurrent clients on Windows XP and only about 180-200 on Windows