Re: IIS Warm Up Period
From: Arsen V. (arsen.NoSpamPlease_at_emergency24.com)
Date: 05/07/04
- Next message: Help Wanted: "RE: IHttpAsyncHandler misbehaving?"
- Previous message: Joe Van Meer: "display columns from 2 tables in datalist"
- In reply to: John Alderson: "Re: IIS Warm Up Period"
- Next in thread: Arsen V.: "Re: IIS Warm Up Period"
- Reply: Arsen V.: "Re: IIS Warm Up Period"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 7 May 2004 09:46:21 -0500
Hi John,
Thanks for your suggestion. This is pretty much what I was looking for. I
did not think of the idea to use IPSECCMD to block the requests! This is
great.
Yes, I do have a Load Balancer in front of the web farm. The code is
stable. However, sometimes due to load there is too much queueing (this only
occurs on IIS 6) and the IIS server shuts down the process.
Thanks,
Arsen
"John Alderson" <jalderson^at^adelphia^dot^net> wrote in message
news:%23uEQk%239MEHA.3292@TK2MSFTNGP11.phx.gbl...
> Arsen,
>
> Do you have multiple web servers in a farm? It wasn't clear from your
> posts. Are you using a hardware load balancer in front like a BigIP or
> similar? If so, you could script up a custom restarter like:
>
> 1. IPSECCMD blocks on tcp/80 and tcp/443 - This should take it out of the
> LB pool in a short time depending on how you have your LB setup to check
> website health.
> 2. IISRESET
> 3. Locally, request your webpages to invoke custom code. Easily
scriptable
> with VBScript/WinHTTP or a variety of command line tools or even WAS as
> David Wang suggests.
> 4. Drop IPSec blocks.
>
> Have you looked at the web garden concept? Maybe it makes sense for you
to
> use > 1 process for this site if you have some semi-stable custom code
that
> needs restarting periodically. Regular restarts of IIS or the OS are
> something that you don't need if you are running stable code. If you do
> seem to need these restarts, this means you have a problem with your
custom
> code that you need to investigate. With stable web components, IIS will
run
> for very long periods.
>
> John Alderson
>
> "Arsen V." <arsen.NoSpamPlease@emergency24.com> wrote in message
> news:%23pHVm87MEHA.3572@tk2msftngp13.phx.gbl...
> > Hi David,
> >
> > How can I prevent the IIS6 server from being "dropped into the live
> > rotation" until the warm up scripts run?
> >
> > What happens now, is that when the computer comes up, IIS starts and
> > immediately attempts to process the requests which queue up and cause
> > problems.
> >
> > Is there a way to tell the IIS to start accepting the requests only
after
> > certain warm up? I need this to be automatic so if IIS is restarted in
the
> > middle of the night it can come back up without problems.
> >
> > Thanks,
> > Arsen
> >
> > "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
> > news:e4LKRnzMEHA.3380@TK2MSFTNGP11.phx.gbl...
> >> No, IIS does not have a "warm up period" feature. It is pretty easy to
> >> script WAST or ACT to custom tailor such a warm-up optimized for your
> >> website, though.
> >>
> >> Websites that have high traffic volume usually devise their own mix of
> >> requests to "warm up" a server and get various applications
pre-compiled,
> >> etc -- this is especially necessary for .Net applications, which incur
a
> > CLR
> >> load-up cost as well as ASP.Net pre-compilation cost. After the server
> >> is
> >> warmed up, then it is dropped into the live rotation.
> >>
> >> There shouldn't be much difference between IIS5 and IIS6 in startup
> >> unless
> >> you're using the health-monitoring features of IIS6 to recycle the
worker
> >> process.
> >>
> >> --
> >> //David
> >> IIS
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >> //
> >> "Arsen V." <arsen.NoSpamPlease@emergency24.com> wrote in message
> >> news:uNF7OkqMEHA.1388@TK2MSFTNGP09.phx.gbl...
> >> Hi,
> >>
> >> We have a website with a very high volume of traffic. The pages are
> > ASP.NET.
> >> There are some configuration settings that get loaded by the Global.asx
> > file
> >> on Application Start event. The load time for those settings is about 3
> >> seconds.
> >>
> >> When the site is running on IIS5 everything is okay.
> >>
> >> When the site is running on IIS6 there are problems. It looks like when
> > IIS
> >> starts and all the requests start coming in it is trying to compile the
> >> ASP.NET CLR and to load the settings in Global.asx. However, since
there
> > are
> >> over 100 requests/second, soon it starts to give Service Unavailable
and
> > log
> >> errors QueueFull in the HTTPERR file.
> >>
> >> If I manually stop the IIS, set the directory security of the website
to
> >> accept only the local requests, execute one request, wait 5 seconds,
and
> >> then change the security to accept all requests, it works great.
> >>
> >> Is there a way to give IIS a warm up time? I think it fails because
there
> >> are so many requests that come right away before the CLR is compiled
and
> > the
> >> load settings in the Global.asx has time to execute.
> >>
> >> Thanks,
> >> Arsen
> >>
> >>
> >>
> >>
> >
> >
>
- Next message: Help Wanted: "RE: IHttpAsyncHandler misbehaving?"
- Previous message: Joe Van Meer: "display columns from 2 tables in datalist"
- In reply to: John Alderson: "Re: IIS Warm Up Period"
- Next in thread: Arsen V.: "Re: IIS Warm Up Period"
- Reply: Arsen V.: "Re: IIS Warm Up Period"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
