Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There are many different factors that could be in play here. Taking a stab at the remark that changing your instancing model on the service had zero effect (big IF here) then its possible the 'bottleneck' is upstream from the service. Either at the web server, or the client load generator.</p> <p>You've got several areas to review for tuning: client, web server, wcf service server - that's assuming there are no network devices in the middle. Pick an end and work towards the other end. Since I'm already making an assumption that its not the service, then I'd start at the client and work my way towards the wcf service.</p> <p><strong>Client</strong><br> What machine is driving the load against the web server? A laptop? A desktop? A dedicated test agent, or a shared one? The client acting as the load generator for purposes of this test is also <strong>susceptible to maxConnections</strong> limitation as this is a client setting. </p> <p>What is the CPU utilization of the client generating load? Could it be that the test driver is just unable to generate enough load to push these boxes? Can you add additional test clients to your test?</p> <p><strong>Web Server</strong><br> What does the <a href="http://msdn.microsoft.com/en-us/library/7w2sway1%28VS.80%29.aspx" rel="nofollow noreferrer">system.net/processModel</a> element look like in machine.config on the ASP.NET web server? Try setting autoConfig = true. This will allow the configuration to auto size based on the 'size' of the machine its running on.</p> <p><strong>WCF Service</strong><br> Review WCF service for any throttling defaults that might be in play and tweak appropriately. See <a href="http://msdn.microsoft.com/en-us/library/system.servicemodel.description.servicethrottlingbehavior.aspx" rel="nofollow noreferrer">ServiceThrottlingBehavior</a> on MSDN.</p> <p>Let us know any changes in behavior you might observe (if any) if you make any changes!</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload