Clustering a .NET Windows Service

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I have build a Windows Service using Microsoft .NET Framework. This
service works listening a port and validating the received messages against a
database. This application have a high availability requirement that must be
achieved by configuring it on a cluster.
When testing the service in a desktop, the use of processor was about
4% and memory about 145mb, but when testing the same service on a cluster,
the use of processor was about 50% and memory about 1.4Gb!
I would like to know if there is some special careful when developing
aplications to work on cluster or this is simply a misconfiguration. Thanks
in advance.
 
Fabio said:
Hi,

I have build a Windows Service using Microsoft .NET Framework. This
service works listening a port and validating the received messages against a
database. This application have a high availability requirement that must be
achieved by configuring it on a cluster.
When testing the service in a desktop, the use of processor was about
4% and memory about 145mb, but when testing the same service on a cluster,
the use of processor was about 50% and memory about 1.4Gb!
I would like to know if there is some special careful when developing
aplications to work on cluster or this is simply a misconfiguration. Thanks
in advance.
Click to expand...

The only few things to consider is that we always have persistent
storage of the services in-process states so that when the service is
being failed over, it knows where to pick up from if you do have a lot
of long running tasks going on with the services. Otherwise, you can
normally get away by configuring your service using "generic service"
resource type.

Unless the "generic service" resource type are not sufficient for you,
then you will need to develop your custom resource type.

Chee Pin
 
Back
Top