cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Level 9

IIS Application Initialization

Jump to solution

Hi All,

I've been trying to get the Application Initialization working for the SolarWinds Orion server, as it is painfully slow loading in the morning (up to 10 minutes sometimes). I've tried to follow the instructions in https://docs.microsoft.com/en-us/iis/get-started/whats-new-in-iis-8/iis-80-application-initializatio..., but don't seem to be seeing any improvements. I've attached the two amended files - is anyone able to assist? Also, there seem to be dozens of web.config files - I amended the one under \InetPub\SolarWinds\, but not sure if that is right.

Any help would be gratefully received!

Thanks,

Richard

0 Kudos
1 Solution

Accepted Solutions
Product Manager
Product Manager

Re: IIS Application Initialization

Jump to solution

Generally, the issue is that the AppPool is spinning down due to lack of use. This is a resource conservation feature that's native to IIS that works great when hosting dozens, or even hundreds of different sites on the same server and need to be conservative with resource usage. In a situation where Orion may be the only application served through IIS, having AppPools spin down when not in use, and then back up again when needed, could be a pain when trying to first access the Orion web interface first thing in the morning. Fortunately, this can be disabled in IIS so the AppPool shuts down less often or not at all.

enter image description here

Note I generally only recommend never recycling the AppPool on Additional Web Servers. If you only have a main Orion server, then I typically set the AppPool to timeout after 36 hours. That usually ensures that the AppPool recycles only on weekends.

View solution in original post

5 Replies
Highlighted
Product Manager
Product Manager

Re: IIS Application Initialization

Jump to solution

  wrote:

Hi All,

I've been trying to get the Application Initialization working for the SolarWinds Orion server, as it is painfully slow loading in the morning (up to 10 minutes sometimes). I've tried to follow the instructions in https://docs.microsoft.com/en-us/iis/get-started/whats-new-in-iis-8/iis-80-application-initializatio..., but don't seem to be seeing any improvements. I've attached the two amended files - is anyone able to assist? Also, there seem to be dozens of web.config files - I amended the one under \InetPub\SolarWinds\, but not sure if that is right.

Any help would be gratefully received!

Thanks,

Richard

Richard, did you end up getting this working?

0 Kudos
Highlighted
Level 9

Re: IIS Application Initialization

Jump to solution

No, unfortunately! In fact, the Application Initialization seems to have made things worse…

0 Kudos
Product Manager
Product Manager

Re: IIS Application Initialization

Jump to solution

Generally, the issue is that the AppPool is spinning down due to lack of use. This is a resource conservation feature that's native to IIS that works great when hosting dozens, or even hundreds of different sites on the same server and need to be conservative with resource usage. In a situation where Orion may be the only application served through IIS, having AppPools spin down when not in use, and then back up again when needed, could be a pain when trying to first access the Orion web interface first thing in the morning. Fortunately, this can be disabled in IIS so the AppPool shuts down less often or not at all.

enter image description here

Note I generally only recommend never recycling the AppPool on Additional Web Servers. If you only have a main Orion server, then I typically set the AppPool to timeout after 36 hours. That usually ensures that the AppPool recycles only on weekends.

View solution in original post

Highlighted
Level 9

Re: IIS Application Initialization

Jump to solution

I'm REALLY glad I found this post. I've been experiencing the same issue, and I went through searches back in THWACK's history and with the support center. From that, I turned the idle time-out to 0 and the garbage collection to happen at 5AM each day... and this caused it to be horrid on startup each day. I started digging more and found various threads talking about startup scripts, and one mentioned the Initialization Engine. So I started looking into that, trying to follow Microsoft's notes, but it seemed weird that such a feature wouldn't be incorporated into Solarwinds by now if it was useful.

Then I Found this, where the "Alwayson" setting is flipped and the idle time out is recommended at 36 hours. So I'm going to give this a crack.

Hopefully this site can be updated to be clearer: Success Center

Highlighted
Product Manager
Product Manager

Re: IIS Application Initialization

Jump to solution

ahbrook  wrote:

I'm REALLY glad I found this post. I've been experiencing the same issue, and I went through searches back in THWACK's history and with the support center. From that, I turned the idle time-out to 0 and the garbage collection to happen at 5AM each day... and this caused it to be horrid on startup each day. I started digging more and found various threads talking about startup scripts, and one mentioned the Initialization Engine. So I started looking into that, trying to follow Microsoft's notes, but it seemed weird that such a feature wouldn't be incorporated into Solarwinds by now if it was useful.

Then I Found this, where the "Alwayson" setting is flipped and the idle time out is recommended at 36 hours. So I'm going to give this a crack.

Hopefully this site can be updated to be clearer: Success Center

Thanks Tony, I've filed the request to update that document for clarity under INFODEV-2255