TCP/IP client server application

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Stefan - 26 May 2004 13:36 GMT

Hi

I have a .net client/server app. My server is able to accept multiple clients and I did some tests; my computer is an Amd 1700+ with 512 Mb Ram, OS - Windows XP, if I have 120 or more clients app conected to server my computer is not responding very well.

Q1. there is a limitation of how many sockets I can open
Q2. if I have 20 clients for e.g. and I close the server my client app has an event ConnectionClosedEvent, this event is fired, but when I have a large number of clients and I kill the server this event is not fired.
Note: I fire this event when I try to read/write something in socket.

Thx for your help.
Best regards
Stefa

Reply to this Message

Chad Z. Hower aka Kudzu - 26 May 2004 19:55 GMT

=?Utf-8?B?U3RlZmFu?= <anonymous@discussions.microsoft.com> wrote in
news:93516FD0-4DE0-43FC-BB03-589CB391F2EE@microsoft.com:

> I have a .net client/server app. My server is able to accept multiple
> clients and I did some tests; my computer is an Amd 1700+ with 512 Mb
> Ram, OS - Windows XP, if I have 120 or more clients app conected to
> server my computer is not responding very well.

You are likely thrashing.

> Q1. there is a limitation of how many sockets I can open ?

Yes, but its WAY above 120. 120 is nothing.

--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"

Empower ASP.NET with IntraWeb
http://www.atozed.com/IntraWeb/

Reply to this Message

Yuancai \(Charlie\) Ye - 27 May 2004 16:08 GMT

Hi,
For supporting more clients, you may have to use window system APIs
directly with full non-blocking socket. Due to limitations of dotNet socket
( window system APIs are great!), you may have performance and scalability
problem when a server has to support many clients. You may see the site
http://www.udaparts.com/articles/articles.htm for some clues.

Signature

Yuancai (Charlie) Ye

Fast and securely accessing all of remote data sources anywhere with
SocketPro using batch/queue, asynchrony and parallel computation with online
compressing

See 30 well-tested and real OLEDB examples

www.udaparts.com

> Hi,
>
> I have a .net client/server app. My server is able to accept multiple clients and I did some tests; my computer is an Amd 1700+ with 512 Mb Ram,

OS - Windows XP, if I have 120 or more clients app conected to server my
computer is not responding very well.

> Q1. there is a limitation of how many sockets I can open ?
> Q2. if I have 20 clients for e.g. and I close the server my client app has an event ConnectionClosedEvent, this event is fired, but when I have a large

number of clients and I kill the server this event is not fired.

> Note: I fire this event when I try to read/write something in socket.
>
> Thx for your help.
> Best regards,
> Stefan

Reply to this Message

Durgaprasad Gorti [MSFT] - 28 May 2004 01:51 GMT

.NET Fully supports non blocking and async sockets. There is
no need to go to the system level APIS.
You can easily architect a multi client app using a set of thread
[like a thread pool and not spawn a thread for each client

Look at the Async Socket APIs and you should be able to do this

Reply to this Message

Yuancai \(Charlie\) Ye - 04 Jun 2004 14:22 GMT

Hi, Durgaprasad Gorti:
For sure I know how to use dotNet version of socket. I can garentee you
that no dotnet socket application can compare with my SocketPro, which is
written from the bottom with 100% support of dotnet environment.

Signature

> .NET Fully supports non blocking and async sockets. There is
> no need to go to the system level APIS.
> You can easily architect a multi client app using a set of threads
> [like a thread pool and not spawn a thread for each client]
>
> Look at the Async Socket APIs and you should be able to do this

Reply to this Message

Durgaprasad Gorti[MSFT] - 05 Jun 2004 09:18 GMT

What makes you think we have not done the same?
Why don't you list the stuff you do and we don't we can then compare

> Hi, Durgaprasad Gorti:
> For sure I know how to use dotNet version of socket. I can garentee you
[quoted text clipped - 7 lines]
> >
> > Look at the Async Socket APIs and you should be able to do this

Reply to this Message

Rate this thread:

TCP/IP client server application

Free Magazines