IIS .Net ASP Performance Tuning

Question

Hi,

Do you have any tips/recommendations for tuning the Adaxes ASP web portals?

We're seeing the common ASP recycle load times etc - do you recommend turning off recycling, doing timed pre-requests to load the compiled app to memory, or any of the other tips you see on Google?!

Rgds

Comments

Hello,

Tweaking IIS settings will hardly result in a considerable performance gain. In fact, if you are experiencing considerable Web Interface performance issues, we don't think those can be related to IIS performance settings.

If you are experiencing considerable performance issues with Adaxes Web Interface sites, could you describe the issues that you experience and your environment in more detail?

---

Hi,

General performance is OK, it's just that we can experience a delay when first loading the site - up to a minute (though sometimes refreshing the page seems to prod it into loading a bit quicker). This is usually first thing in the morning / after a extended period of non-use etc. It's not normally an issue, but if the first time you load the page is during a self-service password reset then it can sit there quite a while (and refreshing is not as simple as clicking the refresh symbol etc).

From what I can gather this is a known issue with .NET applications, and is to do with the recycling of the AppCache pool etc.

Our setup is a Win2008R2 server, with all pre-requisite components installed by the Adaxes installer, and config left at default (IIS, .NET etc).

There are other applications installed on the server (VM), but it has 4GB RAM, 2 cores and no evidence of resource throttling (though we are currently capturing a bit more data on this - using ManageEngine AppManager to collate OS, IIS, .NET and URL performance metrics).

Thanks

Answer 1

Hello,

Judging by what you say, yes, it may be an issue with recycling. To resolve it, you can play with recycling settings for the application pool. For example, you can set it up to occur not so often or play with the events that trigger recycling. In addition to that, you may try using the Miscrosoft's Application Initialization Module. It can help you in optimizing the application pool settings.

Comments

Many Thanks.

We have applied to a test instance and this does appear to have a noticable impact after rebooting/restarting the IIS service. Will monitor after the normal recycling period, and apply to the Live instance if no adverse impacts noted.

One tangental question.

On our base build the Adaxes portal is using the default App Pool, which is v2/integrated. Should we create a dedicated v4 App Pool for Adaxes?

Rgds

---

Hello,

Adaxes should use an Application Pool that uses .NET Framework v.2 and won't work with .NET Framework v.4. You can create a dedicated Application Pool for use by Adaxes, but it should be .NET Framework v.2/integrated