CODEWITHSUNDEEP
asp.net-mvcasp.net-mvc-3asp.net-mvc-4azureazure-web-app-service
SamJolly
SamJolly

Reputation: 6477

Azure Websites, Medium instance, 2 cores, how many application pools?

I have just upgraded my test instance from a small "Standard"(1 core, 1.75gb RAM) instance to medium "Standard" instance (2 cores, 3.5gb RAM), due to potential performance issues, and this seemed a quick hit. We do have issues with application pools recycling and having to rewarm certain code modules. So with a medium instance I am concerned that I might have made our application pool issue worse, by having more than one pool to deal with?

So how many application pools would exist on my Medium Website instance, one or more?

Many thanks in advance.

P.S the other performance issues I believe are linked to the use of In-Proc Session configuration which works

    <sessionState mode="InProc" timeout="30">
       <providers>
          <add name="DefaultSessionProvider" type="System.Web.Providers.DefaultSessionStateProvider, System.Web.Providers, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" connectionStringName="DefaultConnection" />
       </providers>
    </sessionState>

I realise this is periphery to the question, but it might help provide some context.

Upvotes: 0

Views: 177

Answers (1)

ahmelsayed
ahmelsayed

Reputation: 7402

You get 1 application pool per site no matter what size the VM is. an application pool is basically IIS terminology for how the process management (e.g: identity, quotas, number of processes, etc) for your site is carried on. It's really an implementation detail that you shouldn't necessarily worry about.

For your cold start issues, have you considered enabling the Always On setting for your site?

You can also add an entry for Application Initialization to warm any code paths you want to. This is how that would look like in your web.config

<applicationInitialization doAppInitAfterRestart="true" >
   <add initializationPage="/" />
   <add initializationPage="/Page2" />
   <add initializationPage="/Page3" />
</applicationInitialization>

And consider using staged publishing to get around cold starts when you re-publish your site

Upvotes: 2

Related Questions