I deployed my .Net 2.0 (binary,http) Remoting service application on a new 16 core , 8 GB RAM server. The server is 64 bit, and the application is compiled under Any CPU option. Most of the IIS7 settings are default. The app pool is classis .Net 2.0.
I am running a basic one request-at-a-time remoting client to test the application.The requests are being processed extremely slow. I dont see CPU being used more than 1% on any core. and memory usage is 100 MB for the w3wp process
I run this same application code in production under IIS6, on a 4 core server, with 4GB RAM, the application processes millions of queries a day.
I added some cutom profiling to code and the entire processing of a single request is done within less than 100 milliseconds but the overall response time is more than a second. So I have a feeling its the serialization of the request and response thats taking another 900 ms.
Has anybody tested .Net remoting with IIS7, any special settings needed to get this working?
This is really frustrating as we invested in buying new hardware and installed Windows Server 2008. Any help from Microsoft professionals will be greatly appreciated.
Thanks, Abhi