Process Limit?

Hi Guys,

I’m writing a server application, and for each user that connects to the server, a new process is created. I know that’s not a desirable scenario, but its the only way that I can achieve what I am trying to do.

Is there a maximum process limit on Windows XP? RAM is obviously going to be an issue here... lets say that the imaginary machine had 4GB of RAM and a fairly powerful CPU. I’m aiming at 1000 simultaneous users.

Thanks!

I don't know of any limit other than server resources, but I'd really look for some alternative, 1000 processes would be a nightmare to work with even if you can spawn that many.

It's going to be a telnet server. I can’t think of any other way of the client being able to run their console applications (like edit.com) on the server without spawning a new process. I've looked around and this is how all of the other telnet server applications are doing it (although I haven’t looked at the Microsoft Telnet Server, so I can’t vouch for that). Any ideas?

For telnet use you'll probably need to stick with the separate processes. But 1000 simultaneous users is an awful lot

I've worked out that each session takes up just under 3MB of RAM. I've also written an echo server that can support upto 1,500 users and still remain stable, so I'm pretty sure that I can do it on a machine with 4GB of RAM.

Fingers crossed!