 |
|
|
|
Next: Service Pack KB832894 CAUTION HELP?
|
| Author |
Message |
External
Since: Feb 03, 2004
Posts: 7
|
(Msg. 1) Posted: Tue Feb 03, 2004 2:36 pm
Post subject: Slow response on windows server 2003 running multiple web site.
Archived from groups: microsoft>public>inetserver>iis (more info?)
|
|
|
hi.all
just a quick question, has anyone experience a slow response on windows 2k3
running multiple web site.
I have two site running and they are listening on the same port with
different http header, e.g different domain
name, but it seems that the response is very slow. it takes about 4 seconds
for the client browser to start
loading the requested page. the server is running on the AMD 900 with 256 M
of RAM, it might be the
hardware, but I think it's more likely it's the IIS 6 problem. can anyone
explain what's going on?
PS. I was runing those two asp.net app on xp box and it's was fast.
Kevin |
|
| Back to top |
|
 | |
External
Since: Aug 25, 2003
Posts: 2419
|
(Msg. 2) Posted: Thu Feb 05, 2004 7:51 am
Post subject: Re: Slow response on windows server 2003 running multiple web site. [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
ASP.Net applications have a large startup latency, so initial requests to an
ASP.Net application will be slow and that is by-design.
However, the problem on IIS6 is that default IIS6 configuration will
proactively idle-timeout ASP.Net applications after 15 minutes of idleness
as well as every 29 hours, causing the large startup latency to be
repeatedly incurred on the subsequent request.
IIS 5.1 on XP Pro does not proactively idle timeout nor do any sort of
health-monitoring like IIS6, so while it won't repeatedly incur this startup
latency, it does so at the cost of not being reliable.
People have generally noted that the first request is slow but subsequent
requests are fast -- until the 15 minute idleness kicks in -- and this is
the cause.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Kevin" <kyu.TakeThisOut@nrcan.gc.ca> wrote in message
news:%23y3rUSo6DHA.1040@TK2MSFTNGP10.phx.gbl...
hi.all
just a quick question, has anyone experience a slow response on windows 2k3
running multiple web site.
I have two site running and they are listening on the same port with
different http header, e.g different domain
name, but it seems that the response is very slow. it takes about 4 seconds
for the client browser to start
loading the requested page. the server is running on the AMD 900 with 256 M
of RAM, it might be the
hardware, but I think it's more likely it's the IIS 6 problem. can anyone
explain what's going on?
PS. I was runing those two asp.net app on xp box and it's was fast.
Kevin |
|
| Back to top |
|
| |
External
Since: Feb 03, 2004
Posts: 7
|
(Msg. 3) Posted: Thu Feb 05, 2004 11:10 am
Post subject: Re: Slow response on windows server 2003 running multiple web site. [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
"David Wang [Msft]" <someone.TakeThisOut@online.microsoft.com> wrote in message
news:%23PIN2g%236DHA.1592@TK2MSFTNGP10.phx.gbl...
> ASP.Net applications have a large startup latency, so initial requests to
an
> ASP.Net application will be slow and that is by-design.
>
> However, the problem on IIS6 is that default IIS6 configuration will
> proactively idle-timeout ASP.Net applications after 15 minutes of idleness
> as well as every 29 hours, causing the large startup latency to be
> repeatedly incurred on the subsequent request.
>
> IIS 5.1 on XP Pro does not proactively idle timeout nor do any sort of
> health-monitoring like IIS6, so while it won't repeatedly incur this
startup
> latency, it does so at the cost of not being reliable.
>
>
> People have generally noted that the first request is slow but subsequent
> requests are fast -- until the 15 minute idleness kicks in -- and this is
> the cause.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "Kevin" <kyu.TakeThisOut@nrcan.gc.ca> wrote in message
> news:%23y3rUSo6DHA.1040@TK2MSFTNGP10.phx.gbl...
> hi.all
>
> just a quick question, has anyone experience a slow response on windows
2k3
> running multiple web site.
>
> I have two site running and they are listening on the same port with
> different http header, e.g different domain
> name, but it seems that the response is very slow. it takes about 4
seconds
> for the client browser to start
> loading the requested page. the server is running on the AMD 900 with 256
M
> of RAM, it might be the
> hardware, but I think it's more likely it's the IIS 6 problem. can anyone
> explain what's going on?
>
> PS. I was runing those two asp.net app on xp box and it's was fast.
>
> Kevin
>
>
>
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Slow response on windows server 2003 running multiple web .. |
|
| Back to top |
|
| |
External
Since: Feb 03, 2004
Posts: 7
|
(Msg. 4) Posted: Thu Feb 05, 2004 11:15 am
Post subject: Re: Slow response on windows server 2003 running multiple web site. [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
David
Thank you for your response.
but only one of my app is asp.net app, the other is just plain html pages.
it seems like it doesn't matter which site I access first, the other one
will response fast and also a remote user will get fast response from both
sites fast if he access them around the same time. seems like IIS6 app pool
will cache the sites for a certain period of time then timeout the thread
pool.
so the next time a user access the site, it will cache them again.
how can I keep the app pool alive? settting the timeout longer?
Kevin Yu
"David Wang [Msft]" <someone RemoveThis @online.microsoft.com> wrote in message
news:%23PIN2g%236DHA.1592@TK2MSFTNGP10.phx.gbl...
> ASP.Net applications have a large startup latency, so initial requests to
an
> ASP.Net application will be slow and that is by-design.
>
> However, the problem on IIS6 is that default IIS6 configuration will
> proactively idle-timeout ASP.Net applications after 15 minutes of idleness
> as well as every 29 hours, causing the large startup latency to be
> repeatedly incurred on the subsequent request.
>
> IIS 5.1 on XP Pro does not proactively idle timeout nor do any sort of
> health-monitoring like IIS6, so while it won't repeatedly incur this
startup
> latency, it does so at the cost of not being reliable.
>
>
> People have generally noted that the first request is slow but subsequent
> requests are fast -- until the 15 minute idleness kicks in -- and this is
> the cause.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "Kevin" <kyu RemoveThis @nrcan.gc.ca> wrote in message
> news:%23y3rUSo6DHA.1040@TK2MSFTNGP10.phx.gbl...
> hi.all
>
> just a quick question, has anyone experience a slow response on windows
2k3
> running multiple web site.
>
> I have two site running and they are listening on the same port with
> different http header, e.g different domain
> name, but it seems that the response is very slow. it takes about 4
seconds
> for the client browser to start
> loading the requested page. the server is running on the AMD 900 with 256
M
> of RAM, it might be the
> hardware, but I think it's more likely it's the IIS 6 problem. can anyone
> explain what's going on?
>
> PS. I was runing those two asp.net app on xp box and it's was fast.
>
> Kevin
>
>
>
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Slow response on windows server 2003 running multiple web .. |
|
| Back to top |
|
| |
External
Since: Feb 03, 2004
Posts: 7
|
(Msg. 5) Posted: Thu Feb 05, 2004 11:20 am
Post subject: Re: Slow response on windows server 2003 running multiple web site. [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Correction: the response on access to the second site after accessing the
first site is also slow.
"David Wang [Msft]" <someone.RemoveThis@online.microsoft.com> wrote in message
news:%23PIN2g%236DHA.1592@TK2MSFTNGP10.phx.gbl...
> ASP.Net applications have a large startup latency, so initial requests to
an
> ASP.Net application will be slow and that is by-design.
>
> However, the problem on IIS6 is that default IIS6 configuration will
> proactively idle-timeout ASP.Net applications after 15 minutes of idleness
> as well as every 29 hours, causing the large startup latency to be
> repeatedly incurred on the subsequent request.
>
> IIS 5.1 on XP Pro does not proactively idle timeout nor do any sort of
> health-monitoring like IIS6, so while it won't repeatedly incur this
startup
> latency, it does so at the cost of not being reliable.
>
>
> People have generally noted that the first request is slow but subsequent
> requests are fast -- until the 15 minute idleness kicks in -- and this is
> the cause.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "Kevin" <kyu.RemoveThis@nrcan.gc.ca> wrote in message
> news:%23y3rUSo6DHA.1040@TK2MSFTNGP10.phx.gbl...
> hi.all
>
> just a quick question, has anyone experience a slow response on windows
2k3
> running multiple web site.
>
> I have two site running and they are listening on the same port with
> different http header, e.g different domain
> name, but it seems that the response is very slow. it takes about 4
seconds
> for the client browser to start
> loading the requested page. the server is running on the AMD 900 with 256
M
> of RAM, it might be the
> hardware, but I think it's more likely it's the IIS 6 problem. can anyone
> explain what's going on?
>
> PS. I was runing those two asp.net app on xp box and it's was fast.
>
> Kevin
>
>
>
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Slow response on windows server 2003 running multiple web .. |
|
| Back to top |
|
| |
External
Since: Aug 25, 2003
Posts: 2419
|
(Msg. 6) Posted: Fri Feb 06, 2004 3:16 am
Post subject: Re: Slow response on windows server 2003 running multiple web site. [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Based on your description, it sounds like the idle timeout is what is
causing the occassional slowdown (since you say if you access it again at
around the same time, it's fast).
You can keep an AppPool alive by turning off health-monitoring metrics that
I described, such as the 15 minute idle timeout as well as the mandatory
recycle every 29 hours. Check out IIS documentation from F1-help in the IIS
Manager UI.
It is up to you to tune health-monitoring metrics correctly to balance it
with performance and reliability.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Kevin" <kyu.RemoveThis@nrcan.gc.ca> wrote in message
news:eleUwr$6DHA.1040@TK2MSFTNGP10.phx.gbl...
David
Thank you for your response.
but only one of my app is asp.net app, the other is just plain html pages.
it seems like it doesn't matter which site I access first, the other one
will response fast and also a remote user will get fast response from both
sites fast if he access them around the same time. seems like IIS6 app pool
will cache the sites for a certain period of time then timeout the thread
pool.
so the next time a user access the site, it will cache them again.
how can I keep the app pool alive? settting the timeout longer?
Kevin Yu
"David Wang [Msft]" <someone.RemoveThis@online.microsoft.com> wrote in message
news:%23PIN2g%236DHA.1592@TK2MSFTNGP10.phx.gbl...
> ASP.Net applications have a large startup latency, so initial requests to
an
> ASP.Net application will be slow and that is by-design.
>
> However, the problem on IIS6 is that default IIS6 configuration will
> proactively idle-timeout ASP.Net applications after 15 minutes of idleness
> as well as every 29 hours, causing the large startup latency to be
> repeatedly incurred on the subsequent request.
>
> IIS 5.1 on XP Pro does not proactively idle timeout nor do any sort of
> health-monitoring like IIS6, so while it won't repeatedly incur this
startup
> latency, it does so at the cost of not being reliable.
>
>
> People have generally noted that the first request is slow but subsequent
> requests are fast -- until the 15 minute idleness kicks in -- and this is
> the cause.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "Kevin" <kyu.RemoveThis@nrcan.gc.ca> wrote in message
> news:%23y3rUSo6DHA.1040@TK2MSFTNGP10.phx.gbl...
> hi.all
>
> just a quick question, has anyone experience a slow response on windows
2k3
> running multiple web site.
>
> I have two site running and they are listening on the same port with
> different http header, e.g different domain
> name, but it seems that the response is very slow. it takes about 4
seconds
> for the client browser to start
> loading the requested page. the server is running on the AMD 900 with 256
M
> of RAM, it might be the
> hardware, but I think it's more likely it's the IIS 6 problem. can anyone
> explain what's going on?
>
> PS. I was runing those two asp.net app on xp box and it's was fast.
>
> Kevin
>
>
>
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Slow response on windows server 2003 running multiple web .. |
|
| Back to top |
|
| |
External
Since: Feb 03, 2004
Posts: 7
|
(Msg. 7) Posted: Fri Feb 06, 2004 11:09 am
Post subject: Re: Slow response on windows server 2003 running multiple web site. [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Thank you David
I turn off the "shtudown worker process when idle for XX minutes" in the
performance tap. now both site response fast.
Kevin
"David Wang [Msft]" <someone DeleteThis @online.microsoft.com> wrote in message
news:OujryzI7DHA.3860@tk2msftngp13.phx.gbl...
> Based on your description, it sounds like the idle timeout is what is
> causing the occassional slowdown (since you say if you access it again at
> around the same time, it's fast).
>
> You can keep an AppPool alive by turning off health-monitoring metrics
that
> I described, such as the 15 minute idle timeout as well as the mandatory
> recycle every 29 hours. Check out IIS documentation from F1-help in the
IIS
> Manager UI.
>
> It is up to you to tune health-monitoring metrics correctly to balance it
> with performance and reliability.
>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "Kevin" <kyu DeleteThis @nrcan.gc.ca> wrote in message
> news:eleUwr$6DHA.1040@TK2MSFTNGP10.phx.gbl...
> David
>
> Thank you for your response.
> but only one of my app is asp.net app, the other is just plain html pages.
> it seems like it doesn't matter which site I access first, the other one
> will response fast and also a remote user will get fast response from both
> sites fast if he access them around the same time. seems like IIS6 app
pool
> will cache the sites for a certain period of time then timeout the thread
> pool.
> so the next time a user access the site, it will cache them again.
>
> how can I keep the app pool alive? settting the timeout longer?
>
> Kevin Yu
>
>
> "David Wang [Msft]" <someone DeleteThis @online.microsoft.com> wrote in message
> news:%23PIN2g%236DHA.1592@TK2MSFTNGP10.phx.gbl...
> > ASP.Net applications have a large startup latency, so initial requests
to
> an
> > ASP.Net application will be slow and that is by-design.
> >
> > However, the problem on IIS6 is that default IIS6 configuration will
> > proactively idle-timeout ASP.Net applications after 15 minutes of
idleness
> > as well as every 29 hours, causing the large startup latency to be
> > repeatedly incurred on the subsequent request.
> >
> > IIS 5.1 on XP Pro does not proactively idle timeout nor do any sort of
> > health-monitoring like IIS6, so while it won't repeatedly incur this
> startup
> > latency, it does so at the cost of not being reliable.
> >
> >
> > People have generally noted that the first request is slow but
subsequent
> > requests are fast -- until the 15 minute idleness kicks in -- and this
is
> > the cause.
> >
> > --
> > //David
> > IIS
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > //
> > "Kevin" <kyu DeleteThis @nrcan.gc.ca> wrote in message
> > news:%23y3rUSo6DHA.1040@TK2MSFTNGP10.phx.gbl...
> > hi.all
> >
> > just a quick question, has anyone experience a slow response on windows
> 2k3
> > running multiple web site.
> >
> > I have two site running and they are listening on the same port with
> > different http header, e.g different domain
> > name, but it seems that the response is very slow. it takes about 4
> seconds
> > for the client browser to start
> > loading the requested page. the server is running on the AMD 900 with
256
> M
> > of RAM, it might be the
> > hardware, but I think it's more likely it's the IIS 6 problem. can
anyone
> > explain what's going on?
> >
> > PS. I was runing those two asp.net app on xp box and it's was fast.
> >
> > Kevin
> >
> >
> >
> >
>
>
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Slow response on windows server 2003 running multiple web .. |
|
| Back to top |
|
| |
| Related Topics: | Slow response with IIS6.0 - Hello I have an asp.net website installed on a webserver 2003. I notice that the response is very slow on some pages when I asked them from internet. But when I run the site from the server, it is very fast. The site was on a serveur 2000 before and no..
Slow response for apps - Users on intranet get slow response times when entering data into a form. It takes around 8 to 10 seconds for the app to respond. What areas of performance optimization should I be checking out? Thanks!
Intermittant Slow Response Times - If some one could point me in the right direction that would be excellant. Problem is: Since last Monday (1st December) we are having some problems with our web site running on IIS5. Now and again it will sit there saying 'web Site Found. Waiting fo...
IIS 6 Slow running ASP pages - Does anyone know when there will be a fix for the issue causing IIS 6 to process asp pages so slow? I suppose that I would even pay for a fix at this point.
Running Multiple Websites - Hi, I have this problem of starting multiple websites at a time. for example "By default in ISM the Default Web site is started". After i create a new website i want to start the newly created website. But it is giving error saying Requ... |
|
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Profile
Private Messages
Log in
