Biztalk Performance Tuning With WCF Service

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Biztalk Performance Tuning With WCF Service

Viewing 0 reply threads
  • Author
    Posts
    • #23225

      Hi,

      We were doing a Performance Testing of  an Application Running in Biztalk Server 2009 .The Biztalk Sever Application  was calling a .net component which was internally calling the WCF Service.

      The Number Records which were Intended to be processed were 64000.

       

      But when we see the IIS logs of the WCF Service only 2 requests were getting to the IIS per second .

       so this would take nearly hours to process the complete 64000 Records

       

       

      The following Server Setting  Changes were made :

       

       

      The following is an example of the configuration for the maximum connections property: The following setting was made in the Biatalk Config File

      Copy Code

      <configuration>
        <system.net>
          <connectionManagement>
            <add address = "http://www.contoso.com" maxconnection = "20" />
            <add address = "http://www.northwind.com" maxconnection = "20" />
          </connectionManagement>
        </system.net>
      </configuration>

       

       

      Implemented the Service Throtteling Behaviour at the Service .

       

       

      <behaviors> 
        <serviceBehaviors> 
          <behavior name="DefaultThrottlingBehavior"> 
            <serviceThrottling maxConcurrentCalls="16" 
                               maxConcurrentSessions="10" 
                               maxConcurrentInstances="[Int32.MaxValue]" /> 
          </behavior> 
        </serviceBehaviors> 
      </behaviors>
       
       
       

      Tune the MaxPoolThreads registry entry

      This setting specifies the number of pool threads to create per processor. Pool threads watch the network for requests and process incoming requests. The MaxPoolThreads count does not include threads that are consumed by ISAPI applications. Generally, you should not create more than 20 threads per processor. MaxPoolThreads is a REG_DWORD registry entry located at HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\InetInfo\Parameters\ with a default value of 4.
       
       
       
      Asp.net Thread Pool Chnages:
       
                     When I do this change we are getting the error that minFreethreads cannot exceed 400
       
      <system.web>
               <processModel maxWorkerThreads="100" maxIoThreads="100" minWorkerThreads="50"/>
               <httpRuntime minFreeThreads="704" minLocalRequestFreeThreads="608"/>
      </system.web>
       
       

       

Viewing 0 reply threads
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.