in reply to maximum number of open ports per process on win98

I ran into the same sorts of limitations earlier this year while trying to write a simulation server for testing code at work. I ended up trying several things including arrays of select objects under 5.6 and pure blocking sockets in their own threads under 5.8. I tried it under both linux and Win2k with about the same results.

Anytime I got past the 64 limits I seem to run into another limit around 110-125 or so. I did not try a select object per thread under 5.8 and perhaps when there's time I will. However, I need to service about 1000 sockets simultaneously and just couldn't get it to work very well even at around 100, performance dropped off. Unfortunately I ended up doing it in java which is working pretty well. For everything else I do, Perl rocks!

Perhaps Perl 6.? will have a better setup for this issue.

  • Comment on Re: maximum number of open ports per process on win98

Replies are listed 'Best First'.
Re: Re: maximum number of open ports per process on win98
by Anonymous Monk on Nov 28, 2003 at 23:31 UTC
    I ran into the exact same results and limitations myself. Ran some test on Win2k with the latest ActiveState Python 2.3.2 build. It has its limit at 512 sockets on a select. using its multi-threading, I got up to 2000 threads using blocking sockets. I could not create any more threads at that point. a non-blocking multiplexing approach using arrays of 512 sockets using select got me 4000 sockets ok. That is where I stopped.