>
> Yes, you can have maximum 64k sockets on single domain, but you can also
> have few domains (few IP's).
Yes, usually spread around a server farm, ie. multiple machines.
The worst thing is amount of non-paged memory
> (non-paged pool), where socket's data resides. Assuming single socket uses
4
> KB of memory there's about 200 MB needed to serve 50,000 sockets. Commonly
> non-paged pool size is equal to quarter of amount of physical RAM, so
> theoretically you can have 512 MB pool with 2GB RAM on 32 bit Windows (or
> 768 MB with 3GB address space - special boot switch needed). Too bad
Windows
> 2000 have upper limit set to 256 MB, I dont remember what are limits on
> newer Microsoft OS's, but since 64 bit Windows provides few terabytes of
> address space limits should be higher.
Empirically, I have had 24k sockets open on a 256Mb box, 12k on the server
and 12k on the test client app. Non-paged pool did not seem to be a problem.
I remember this issue being brought up before and I remember checking the
remaining non-paged pool in the task manager & deciding it was OK.
Unfortunately, I did not record the exact figures. I do remember that the
system worked OK with all those sockets open - the Word, notepad, IE, OE
etc. I always have lying around on the taskbar all still worked fine.
Rgds,
Martin
