Process Memory Limitation & IIS

[=?Utf-8?B?UmFzaGVlZA==?=]

We have distributed application built upon .NET 2.0. The business components
are exposed as Web Services. Some of the Business Components involves in
heavy processing and occupies more RAM. It appears there is a memory
limitation of 4 GB per process and we are not sure if we have to further
distribute the heavy processing components in to separate process/application
domain. We use II6 6.0 and Windows 2003 to hosts all Web services. Currently
all Web Services are part of single Application Domain.

To over come the 4GB limitation, we are planning to isolate the heave
processing components out of process using the below options.

1.Isolate the heavy processing components which use more memory using .NET
remoting (The application server will invoke these components using .NET
remoting). This way, we have a dedicated process established for heavy
processing components.
2.Create a new Web site to host heavy processing components. They will be
exposed as Web services similar to application server components. The
application server will make use the new web service so that the processing
happens in a different application domain. We are really not sure whether
this approach addresses the 4GB limitation per process. Otherwise we will
have to go for #1

Please note all the above should work within single application server. The
hardware typically contains multiple processors and can accommodate more
memory (8 GB). Any inputs on the above would be really helpful. We will have
to pickup the right solution from the above options.

We are still researching IIS 6.0 architecture to make sure item #2 above is
feasible in this context.

Thanks,
Rasheed

[Timothy Walton]

We have distributed application built upon .NET 2.0. The business components
are exposed as Web Services. Some of the Business Components involves in
heavy processing and occupies more RAM. It appears there is a memory
limitation of 4 GB per process and we are not sure if we have to further
distribute the heavy processing components in to separate process/application
domain. We use II6 6.0 and Windows 2003 to hosts all Web services. Currently
all Web Services are part of single Application Domain.

To over come the 4GB limitation, we are planning to isolate the heave
processing components out of process using the below options.

1.Isolate the heavy processing components which use more memory using .NET
remoting (The application server will invoke these components using .NET
remoting). This way, we have a dedicated process established for heavy
processing components.
2.Create a new Web site to host heavy processing components. They will be
exposed as Web services similar to application server components. The
application server will make use the new web service so that the processing
happens in a different application domain. We are really not sure whether
this approach addresses the 4GB limitation per process. Otherwise we will
have to go for #1

Please note all the above should work within single application server. The
hardware typically contains multiple processors and can accommodate more
memory (8 GB). Any inputs on the above would be really helpful. We will have
to pickup the right solution from the above options.

We are still researching IIS 6.0 architecture to make sure item #2 above is
feasible in this context.

Thanks,
Rasheed

Is this 64bit ?

BizTalk Utilities - Frustration free BizTalk Adapters
http://www.topxml.com/biztalkutilities