ASP.NET shares resources in the same pool?

Asked

Viewed 105 times

4

I have today on my IIS 8 sites on ASP.NET using the same pool. On average they consume 800mb of RAM.

I ended up dismembering them (separate pools) and it seems to be consuming 1,5GB in total.

I wonder if IIS shares resources in the same pool?

Ex: the Entity Framework.dll it is loaded once and used among all sites of the same pool?

Because several . dll are the same for almost all projects: Ex:

    Antlr3.Runtime.dll
    EntityFramework.dll
    EntityFramework.SqlServer.dll
    Newtonsoft.Json.dll
    System.Web.Mvc.dll
    WebGrease.dll
    //etc
asp.net windows iis-7

1 answer

4


You can share IIS resources as you mentioned, but not automatically. To do this. you need to configure your IIS for this. You can see a little here. There are also some examples here and here.

But because the memory consumption increased then?

Each application pool is an instance of W3wp.exe, a working process for one/sets of websites. That is, when it was on the same pool, was creating only one instance, thus consuming memory.

Then I must leave everything in the same application pool?

Not quite so, each case is a case. Stackoverflow, for example, leaves everything in one pool, as the Roberta speaks in her talk, but that means that if any of them get into trouble and for the pool, all the sites will stop working.

In short, you should study what’s best for your case. You can share resources between pools different, put in the same or if you have no problem with the memory, leave as it is.

Note: when sharing resources (dll’s), you must ensure that the systems are using the same version, you may have problems if any are in different version.

  • The increase in consumption of Ram tbm can be other factors such as volume in the accesses, etc. However, I was wondering if it was not the sharing, because the first access on a site is always slow then it is fast. But I had never set up iis to share

  • @Dorathoto The first access is slow for some factors, the most likely is the caching, but this is something else. The accesses I do not know how to say (without monitoring), but increase 50% practically I would say that it is not for the accesses. Now, the process can be the key factor. You can monitor to be sure, but there is also another subject. Otherwise, I hope to have helped.

Browser other questions tagged asp.net windows iis-7

You are not signed in. Login or sign up in order to post.