performance boost by changing Web.Config setting

Coordinator
Oct 27, 2011 at 1:14 AM
Edited Jan 7, 2012 at 4:55 AM

Change your Web.Config as follows for performance enhancement to AVFP (the <clear/> removes unnecessary .NET objects from memory):

for ASP.NET 2.0 (IIS 7, IIS 7.5) VISTA and above:

 

<httpModules>
      <clear/>
      <add name="HttpModule_ProcessManifest" type="MazeComputer.AspManifestHelpers.HttpModule_ProcessManifest, AspManifestHelpers" />
      <add name="Session" type="System.Web.SessionState.SessionStateModule"/>
</httpModules>

 

------------------------------------------------

IIS 6 (ASP.NET 2.0) Windows Server 2003 requires System.Web.SessionState.SessionStateModule for some reason:

 

<httpModules>
      <clear/>
      <add name="HttpModule_ProcessManifest" type="MazeComputer.AspManifestHelpers.HttpModule_ProcessManifest, AspManifestHelpers" />
      <add name="Session" type="System.Web.SessionState.SessionStateModule"/>
</httpModules>

 

------------------------------------------------

ASP.NET 1.1 at GoDaddy also needs Session:

 

<httpModules>
      <clear/>
      <add name="Session" type="System.Web.SessionState.SessionStateModule"/>
</httpModules>

 

 This is within the <system.web> .... </system.web>  section.

Coordinator
Oct 27, 2011 at 8:20 PM
Edited Oct 27, 2011 at 10:17 PM

Are you saying delete everything from the current Web.config and replace it by the values above depending if you are using ASP.NET 1.1 or 2.0? What's with the MazeComputer?

Coordinator
Oct 27, 2011 at 10:17 PM

No, just replace the <httpModules> section - everything else remains intact.

Oct 27, 2011 at 11:29 PM
Edited Oct 27, 2011 at 11:46 PM

Claude.  My Web.Config looks like the following. It does not contain a httpModules section.

P.S. I just got done putting it on my GoDaddy hosting account.  It Works!!! (mostly).  The email demo doesn't work nor does the SQL connection. 

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
   
  <system.web>

    <!--  DYNAMIC DEBUG COMPILATION
          Set compilation debug="true" to enable ASPX debugging.  Otherwise, setting this value to
          false will improve runtime performance of this application.
          Set compilation debug="true" to insert debugging symbols (.pdb information)
          into the compiled page. Because this creates a larger file that executes
          more slowly, you should set this value to true only when debugging and to
          false at all other times. For more information, refer to the documentation about
          debugging ASP.NET files.
    -->
    <compilation
         defaultLanguage="c#"
         debug="true"
    />

    <!--  CUSTOM ERROR MESSAGES
          Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable.
          Add <error> tags for each of the errors you want to handle.

          "On" Always display custom (friendly) messages.
          "Off" Always display detailed ASP.NET error information.
          "RemoteOnly" Display custom (friendly) messages only to users not running
           on the local Web server. This setting is recommended for security purposes, so
           that you do not display application detail information to remote clients.
    -->
    <customErrors
    mode="Off"
    />

    <!--  AUTHENTICATION
          This section sets the authentication policies of the application. Possible modes are "Windows",
          "Forms", "Passport" and "None"

          "None" No authentication is performed.
          "Windows" IIS performs authentication (Basic, Digest, or Integrated Windows) according to
           its settings for the application. Anonymous access must be disabled in IIS.
          "Forms" You provide a custom form (Web page) for users to enter their credentials, and then
           you authenticate them in your application. A user credential token is stored in a cookie.
          "Passport" Authentication is performed via a centralized authentication service provided
           by Microsoft that offers a single logon and core profile services for member sites.
    -->
    <authentication mode="Windows" />

 <!--  AUTHORIZATION
          This section sets the authorization policies of the application. You can allow or deny access
          to application resources by user or role. Wildcards: "*" mean everyone, "?" means anonymous
          (unauthenticated) users.
    -->

    <authorization>
        <allow users="*" /> <!-- Allow all users -->
            <!--  <allow     users="[comma separated list of users]"
                             roles="[comma separated list of roles]"/>
                  <deny      users="[comma separated list of users]"
                             roles="[comma separated list of roles]"/>
            -->
    </authorization>

    <!--  APPLICATION-LEVEL TRACE LOGGING
          Application-level tracing enables trace log output for every page within an application.
          Set trace enabled="true" to enable application trace logging.  If pageOutput="true", the
          trace information will be displayed at the bottom of each page.  Otherwise, you can view the
          application trace log by browsing the "trace.axd" page from your web application
          root.
    -->
    <trace
        enabled="false"
        requestLimit="10"
        pageOutput="false"
        traceMode="SortByTime"
  localOnly="true"
    />

    <!--  SESSION STATE SETTINGS
          By default ASP.NET uses cookies to identify which requests belong to a particular session.
          If cookies are not available, a session can be tracked by adding a session identifier to the URL.
          To disable cookies, set sessionState cookieless="true".
    -->
    <sessionState
            mode="InProc"
            stateConnectionString="tcpip=127.0.0.1:42424"
            sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes"
            cookieless="false"
            timeout="20"
    />

    <!--  GLOBALIZATION
          This section sets the globalization settings of the application.
    -->
    <globalization
            requestEncoding="utf-8"
            responseEncoding="utf-8"
   />

 </system.web>

</configuration>

Coordinator
Oct 27, 2011 at 11:57 PM

Look at some examples on the web.  For the supplied 1.1 web.config, you can add it in the proper place once you understand what section to put it in (from the example you find)

All of this is optional so I wouldn't agonize over this unless you're currently trying to optimize for performance..

 

For e-mail and SQL, take the 'view source;' option to see how thay're set up in the demo.

Coordinator
Dec 6, 2011 at 1:29 PM

Here's what works at GoDaddy (ASP.NET 1.1):

<httpModules>
      <clear/>
      <add name="Session" type="System.Web.SessionState.SessionStateModule"/>
</httpModules>

 

This is within the <system.web> .... </system.web>  section.