Have Geek Brain

Performance degradation when an IIS / ASP application in a virtual directory is converted to a new website with a dedicated IP address

I have an asp.net application running in a virtual directory on the default IIS website.

After deploying this on its own website with its own IP address (on the same computer), performance degrades dramatically.

My first guess might be that this might be some sort of routing issue, but I'm not too keen after all, so I'm not sure where to start over. Or maybe it's something completely different?

UPDATE: Everything else in this scenario remained the same, essentially a new website was created with a static IP pointing to a new folder where all files from the virtual directory were copied to xcopied.

The whole site seems to be slow (but it changes over time) .... images, scripts, you name it. There is no incredibly unusual amount of memory or processor.

Is it possible it will be some kind of routing problem? And if so, how would the person begin to diagnose it?

0


a source to share


1 answer


You should use ASP.Net tracing to determine if your application is slow or a network configuration issue.

You can enable page level tracing by adding the Trace="true"

to page directive to aspx:

<%@ Page Trace="true" %>

or you can alternatively enable tracing for the whole application via web.config:



<configuration>
  <system.web>
    <trace enabled="true" requestLimit="40" localOnly="false"/>
  </system.web>
</configuration>

Read more on MSDN Articles on ASP.Net Trace .

My rates (I had problems):

  • ASP.Net configuration issues
    • The default values ​​for some important parameters are machine.config

      very low. You should check the following parameters:
      • maxconnection

      • maxIoThreads

      • maxWorkerThreads

      • minFreeThreads

      • minLocalRequestFreeThreads

    • Here is the description and recommended values: Tuning IIS 6.0 for performance
  • Database problems
    • the database is on another server and the application was very frequent (many small queries)
    • on a different server and a poorly configured internal network causing latency

  • Network configuration problem

    • check routing
    • network call admin

    Check out this SO question for a few more ideas: The bottleneck conundrum in ASP.NET

+3


a source






More articles:


All Articles