By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
458,088 Members | 1,326 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 458,088 IT Pros & Developers. It's quick & easy.

Maximum sockets at a time

P: 9

i have a Socket based application that works well. The application connects remote servers and getting data from them.

When i try to read data from 20-30 servers at the same time, i works well. But when i try to read 500-1000 server at the same time, it works so slow. The connection requests wait so much although i use async socket methods.

I have suspicion that windows limits the number of sockets can be created at the same time.

If windows limits that, then how can i learn the maximum number of sockets that can be created and transfer data at a time. If there is no limit, then what can my problem be?

Any idea?
Aug 14 '09 #1
Share this Question
Share on Google+
4 Replies

Expert 2.5K+
P: 3,525
What flavor of windows?
If you don't have a sever edition and enough licenses for enough connections... then you get those results.
Aug 14 '09 #2

P: 9
I am running windows xp professional and all licenses are okay. I will test at on windows server 2003 too on monday. I wonder if there is a limitation or caused by my bad design?
Aug 15 '09 #3

Expert 5K+
P: 7,872
I thought that only applied to IIS?
Aug 18 '09 #4

Expert 2.5K+
P: 3,525
Nope. My company sees it all the time when a customer tries to run an XPpro box as the 'server' to 30 client stations. XPpro doesn't allow that many simultaneous connections. So stations keep loosing their connection to shared folders or the server application.
Aug 18 '09 #5

Post your reply

Sign in to post your reply or Sign up for a free account.