.NET Remoting and Load balancing

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Vinc - 13 Jan 2005 02:03 GMT

My scenario is that I have a window service sitting in a server that take
care of processing our backend business logic. Our clients does .NET remoting
call to our server for data processing.

Recently, we are looking at expanding this service by scaling out servers to
serve more clients. I understand that this can be done if I load balance the
servers.

I have read articles that .NET remoting uses one TCP session per application
and waited for 10secs idle time before rendering it to TIME_WAIT state and
eventually destroying the session after four minutes.

Can anyone advice how I can achieve full and true loadbalancing in .NET
remoting as our clients can be sending requests very frequent (<10 secs
intervals).

Reply to this Message

Red Devil - 13 Jan 2005 02:35 GMT

Well, TCP and Sockets may help you to achieve the true NLB

> My scenario is that I have a window service sitting in a server that take
> care of processing our backend business logic. Our clients does .NET remoting
[quoted text clipped - 11 lines]
> remoting as our clients can be sending requests very frequent (<10 secs
> intervals).

Reply to this Message

Sam Santiago - 13 Jan 2005 08:06 GMT

I would read these two articles:

INFO: Configurations That Microsoft Supports for Microsoft .NET Remoting
with Network Load Balancing
http://support.microsoft.com/default.aspx?scid=kb;en-us;830217

and

Improving Remoting Performance
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scal
enetchapt11.asp

These articles state two important things:

1) You cannot load balance with the TCPChannel because it has machine
affinity. HTTPChannel will work.
2) You can only load balance SingleCall SAOs. Not sure if this is strictly
if you NLB services only or if still applies if you have a hardware load
balance solution.

Thanks,

Sam

Signature

_______________________________
Sam Santiago
ssantiago@n0spam-SoftiTechture.com
http://www.SoftiTechture.com
_______________________________

> Well, TCP and Sockets may help you to achieve the true NLB
>
[quoted text clipped - 18 lines]
>> remoting as our clients can be sending requests very frequent (<10 secs
>> intervals).

Reply to this Message

Vinc - 13 Jan 2005 09:13 GMT

Thanks Sam,

Given Http will degrade performance, I think I would give a try to explore
Aysnc TCP methods. Since the parameters I have are of basic type, ie, int,
string etc, I think passing those in network stream should not cause problem.

But I would like your view on using Aysnc TCP as a replacement of .NET
remoting. Can you draw some pro and cons between them? Thanks again.

> I would read these two articles:
>
[quoted text clipped - 41 lines]
> >> remoting as our clients can be sending requests very frequent (<10 secs
> >> intervals).

Reply to this Message

Sam Santiago - 13 Jan 2005 16:42 GMT

I haven't done much with Async TCP, so I cannot provide any information
there.

You might want to check out this article on performance with remoting,
binary serialization, and http:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/bdad
otnetarch14.asp

Thanks,

Sam

Signature

_______________________________
Sam Santiago
ssantiago@n0spam-SoftiTechture.com
http://www.SoftiTechture.com
_______________________________

> Thanks Sam,
>
[quoted text clipped - 57 lines]
>> >> secs
>> >> intervals).

Reply to this Message

Vinc - 14 Jan 2005 14:01 GMT

Thanks Sam,

I will try Async Socket anyway.

> I haven't done much with Async TCP, so I cannot provide any information
> there.
[quoted text clipped - 68 lines]
> >> >> secs
> >> >> intervals).

Reply to this Message

AndreasW - 15 Jan 2005 19:49 GMT

Hi,

If NLB is not what you want, I think, you should change your
communication-framework to enterprise services.

There you can use CLB (Component Load Balancing)
See also:
http://www.microsoft.com/technet/prodtechnol/acs/deploy/clbovrvw.mspx

> Thanks Sam,
>
[quoted text clipped - 72 lines]
> > >> >> secs
> > >> >> intervals).

Reply to this Message

Vinc - 16 Jan 2005 01:47 GMT

Hi AndreasW,

CLB is something I have not consider yet. I will look into the possiblity of
that. Thanks.

> Hi,
>
[quoted text clipped - 81 lines]
> > > >> >> secs
> > > >> >> intervals).

Reply to this Message

Chee Pin Cheam - 16 Mar 2005 17:11 GMT

> Hi AndreasW,
>
> CLB is something I have not consider yet. I will look into the possiblity of
> that. Thanks.

Component Load Balancing mechanism is designed around COM+ 1.x. You
won't be able to use it unless you are using .net enterprise services
(aka servicedcomponent).

Chee PIn

Reply to this Message

.NET Remoting and Load balancing

Free Magazines