SOA Service Throttling on HPC R2 RRS feed

  • Question

  • On HPC (v2), we made use of the node, socket, and core resource type selection and our SOA service ran fine using any of the three types.

    Now, on HPC R2, we are finding that our service works well using the core resource type, but runs into problems with node and socket. Examining the output that our service writes, it appears that when using these two resource types, our service is trying to run multiple calls concurrently.

    Looking through the documentation, it seems like the remarks on this MSDN page (http://msdn.microsoft.com/en-us/library/microsoft.hpc.scheduler.session.sessionstartinfo.sessionresourceunittype%28VS.85%29.aspx) are applicable.

    We have tried setting the serviceThrottling maxConcurrentCalls to 1 in the service.config file for our service, but we are still having the same troubles.

    Is there some additional change required on HPC R2 that we might have missed?

    Thursday, February 3, 2011 5:18 PM


  • maxConcurrentCalls has been moved to serviceregistration section in R2 - http://msdn.microsoft.com/en-us/library/ff943786(v=WS.10).aspx.

        <service assembly="%CCP_HOME%bin\EchoSvcLib.dll"
                 serviceInitializationTimeout="60000" >
          <!--Below is a sample for adding environment variables to the service-->
            <add name="myname1" value="myvalue1"/>
            <add name="myname2" value="myvalue2"/>

    We normally update MSDN/TechNet together with our product release. However, the throttling service behavior description on the link you gave is clearly out of date. Thanks for finding the problem. We'll change that.

    • Marked as answer by Derek Kivi Thursday, March 3, 2011 5:14 PM
    Wednesday, February 23, 2011 8:26 PM