 |
|
|
|
Next: Memory Leak and caching
|
| Author |
Message |
External
Since: Aug 25, 2003
Posts: 1
|
(Msg. 1) Posted: Mon Aug 25, 2003 12:59 pm
Post subject: Multiple requests for the same page from the same user are being kept in the asp
Archived from groups: microsoft>public>inetserver>iis (more info?)
|
|
|
Hi,
I'm having a problem with server too busy conditions, and I found a strange
behavior watching IIS process the page requests.
Using IISTracer (http://www.pstruh.cz/help/iistrace) to analyze which pages
IIS is processing at a moment I can see frequently why the asp requests
queue raises and goes down so frequently (from zero up to 50 requests, and
then to zero in less then 30 seconds).
Almost all the time this behavior happens because of multiple requests being
kept in the queue from the same user, for the same page (I can see what page
is being requested and other parameters, like session cookies, that can
identify the user).
Sometimes there are more than 10 requests like that for one user, and they
stay in the queue until one of them is served.
At this time this page, and all the "clone" requests, is taken out of the
queue.
I can see this happening in the IISTracer page and in the performance
graphics for the ASP object.
Anyone knows why this is happening?
Thanks a lot,
Alexandre |
|
| Back to top |
|
 | |
External
Since: Aug 26, 2003
Posts: 22
|
(Msg. 2) Posted: Wed Aug 27, 2003 3:28 am
Post subject: RE: Multiple requests for the same page from the same user are being kept in the [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Multiple requests from the same session are handled by the same thread
within IIS.
So suppose a user makes a request, and that request takes a while to serve.
Perhaps the page needs to connect to a database, and the database is
temporarily down or too busy to handle new requests. The user gets
impatient, and hits stop and then refresh a couple of times. This fires up
some new requests, but since they are from the same session as the first
request, they will execute on the thread that is still busy executing that
first request. You'll see the number of ASP requests queued go up each time
the user hits refresh.
When the first request finally finishes executing, the rest of the requests
will have their chance to execute and will leave the queue.
Does that make sense?
-Lisa
> I'm having a problem with server too busy conditions, and I found a
strange
> behavior watching IIS process the page requests.
>
> Using IISTracer (http://www.pstruh.cz/help/iistrace) to analyze which
pages
> IIS is processing at a moment I can see frequently why the asp requests
> queue raises and goes down so frequently (from zero up to 50 requests, and
> then to zero in less then 30 seconds).
>
> Almost all the time this behavior happens because of multiple requests
being
> kept in the queue from the same user, for the same page (I can see what
page
> is being requested and other parameters, like session cookies, that can
> identify the user).
>
> Sometimes there are more than 10 requests like that for one user, and they
> stay in the queue until one of them is served.
>
> At this time this page, and all the "clone" requests, is taken out of the
> queue.
>
> I can see this happening in the IISTracer page and in the performance
> graphics for the ASP object.
>
>
>
> Anyone knows why this is happening?
-----
This posting is provided "AS IS" with no warranties, and confers
no rights. You assume all risk for your use.
© 2003 Microsoft Corporation. All rights reserved.<!-- ~MESSAGE_AFTER~ --> |
|
| Back to top |
|
| |
External
Since: Aug 26, 2003
Posts: 171
|
(Msg. 3) Posted: Wed Aug 27, 2003 3:28 am
Post subject: Re: Multiple requests for the same page from the same user are being kept in the [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
No it does not. are you saying that if you open a second window (that will
share the same session cookie) your requests from those two windows are
going to be serialized? I don't think so. This is more likely caused by HTTP
pipelining where IIS has to serialize requests coming over each client
connection (that's connection, not session).
Are you serious that IIS serializes all session requests?
Jerry
"Lisa Cozzens [MSFT]" <lcozzens.RemoveThis@online.microsoft.com> wrote in message
news:Tidy7IDbDHA.2108@cpmsftngxa06.phx.gbl...
> Multiple requests from the same session are handled by the same thread
> within IIS.
>
> So suppose a user makes a request, and that request takes a while to
serve.
> Perhaps the page needs to connect to a database, and the database is
> temporarily down or too busy to handle new requests. The user gets
> impatient, and hits stop and then refresh a couple of times. This fires up
> some new requests, but since they are from the same session as the first
> request, they will execute on the thread that is still busy executing that
> first request. You'll see the number of ASP requests queued go up each
time
> the user hits refresh.
>
> When the first request finally finishes executing, the rest of the
requests
> will have their chance to execute and will leave the queue.
>
> Does that make sense?
>
> -Lisa
>
> > I'm having a problem with server too busy conditions, and I found a
> strange
> > behavior watching IIS process the page requests.
> >
> > Using IISTracer (http://www.pstruh.cz/help/iistrace) to analyze which
> pages
> > IIS is processing at a moment I can see frequently why the asp requests
> > queue raises and goes down so frequently (from zero up to 50 requests,
and
> > then to zero in less then 30 seconds).
> >
> > Almost all the time this behavior happens because of multiple requests
> being
> > kept in the queue from the same user, for the same page (I can see what
> page
> > is being requested and other parameters, like session cookies, that can
> > identify the user).
> >
> > Sometimes there are more than 10 requests like that for one user, and
they
> > stay in the queue until one of them is served.
> >
> > At this time this page, and all the "clone" requests, is taken out of
the
> > queue.
> >
> > I can see this happening in the IISTracer page and in the performance
> > graphics for the ASP object.
> >
> >
> >
> > Anyone knows why this is happening?
>
> -----
> This posting is provided "AS IS" with no warranties, and confers
> no rights. You assume all risk for your use.
> © 2003 Microsoft Corporation. All rights reserved.
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Multiple requests for the same page from the same user are.. |
|
| Back to top |
|
| |
External
Since: Aug 26, 2003
Posts: 22
|
(Msg. 4) Posted: Wed Aug 27, 2003 11:17 pm
Post subject: Re: Multiple requests for the same page from the same user are being kept in the [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
> No it does not. are you saying that if you open a second window (that will
> share the same session cookie) your requests from those two windows are
> going to be serialized? I don't think so. This is more likely caused by
HTTP
> pipelining where IIS has to serialize requests coming over each client
> connection (that's connection, not session).
>
> Are you serious that IIS serializes all session requests?
Yes, IIS serializes all session requests.
244298 PRB: User Requests to Active Server Pages Serialize from the Browser
<a style='text-decoration: underline;' href="http://support.microsoft.com/?id=244298" target="_blank">http://support.microsoft.com/?id=244298</a>
-Lisa
> "Lisa Cozzens [MSFT]" <lcozzens DeleteThis @online.microsoft.com> wrote in message
> news:Tidy7IDbDHA.2108@cpmsftngxa06.phx.gbl...
> > Multiple requests from the same session are handled by the same thread
> > within IIS.
> >
> > So suppose a user makes a request, and that request takes a while to
> serve.
> > Perhaps the page needs to connect to a database, and the database is
> > temporarily down or too busy to handle new requests. The user gets
> > impatient, and hits stop and then refresh a couple of times. This fires
up
> > some new requests, but since they are from the same session as the first
> > request, they will execute on the thread that is still busy executing
that
> > first request. You'll see the number of ASP requests queued go up each
> time
> > the user hits refresh.
> >
> > When the first request finally finishes executing, the rest of the
> requests
> > will have their chance to execute and will leave the queue.
> >
> > Does that make sense?
> >
> > -Lisa
> >
> > > I'm having a problem with server too busy conditions, and I found a
> > strange
> > > behavior watching IIS process the page requests.
> > >
> > > Using IISTracer (http://www.pstruh.cz/help/iistrace) to analyze which
> > pages
> > > IIS is processing at a moment I can see frequently why the asp
requests
> > > queue raises and goes down so frequently (from zero up to 50 requests,
> and
> > > then to zero in less then 30 seconds).
> > >
> > > Almost all the time this behavior happens because of multiple requests
> > being
> > > kept in the queue from the same user, for the same page (I can see
what
> > page
> > > is being requested and other parameters, like session cookies, that
can
> > > identify the user).
> > >
> > > Sometimes there are more than 10 requests like that for one user, and
> they
> > > stay in the queue until one of them is served.
> > >
> > > At this time this page, and all the "clone" requests, is taken out of
> the
> > > queue.
> > >
> > > I can see this happening in the IISTracer page and in the performance
> > > graphics for the ASP object.
> > >
> > >
> > >
> > > Anyone knows why this is happening?
> >
> > -----
> > This posting is provided "AS IS" with no warranties, and confers
> > no rights. You assume all risk for your use.
> > © 2003 Microsoft Corporation. All rights reserved.
> >
>
>
>
-----
This posting is provided "AS IS" with no warranties, and confers
no rights. You assume all risk for your use.
© 2003 Microsoft Corporation. All rights reserved.<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Multiple requests for the same page from the same user are.. |
|
| Back to top |
|
| |
External
Since: Aug 26, 2003
Posts: 171
|
(Msg. 5) Posted: Wed Aug 27, 2003 11:17 pm
Post subject: Re: Multiple requests for the same page from the same user are being kept in the [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Is there a way to disable this? It's definitely something that's going to
kill performance and scalability once you get past simple site with two asp
pages (and use ASP pages to generate images stored in a database for
example, there's absolutely no need to serialize requests like that).
If this is indeed true than ASP is definitely not a scalable solution for a
server application.
Jerry
"Lisa Cozzens [MSFT]" <lcozzens.RemoveThis@online.microsoft.com> wrote in message
news:gchmRhNbDHA.2108@cpmsftngxa06.phx.gbl...
> > No it does not. are you saying that if you open a second window (that
will
> > share the same session cookie) your requests from those two windows are
> > going to be serialized? I don't think so. This is more likely caused by
> HTTP
> > pipelining where IIS has to serialize requests coming over each client
> > connection (that's connection, not session).
> >
> > Are you serious that IIS serializes all session requests?
>
> Yes, IIS serializes all session requests.
>
> 244298 PRB: User Requests to Active Server Pages Serialize from the
Browser
<font color=purple> > <a style='text-decoration: underline;' href="http://support.microsoft.com/?id=244298</font" target="_blank">http://support.microsoft.com/?id=244298</font</a>>
>
> -Lisa
>
> > "Lisa Cozzens [MSFT]" <lcozzens.RemoveThis@online.microsoft.com> wrote in message
> > news:Tidy7IDbDHA.2108@cpmsftngxa06.phx.gbl...
> > > Multiple requests from the same session are handled by the same thread
> > > within IIS.
> > >
> > > So suppose a user makes a request, and that request takes a while to
> > serve.
> > > Perhaps the page needs to connect to a database, and the database is
> > > temporarily down or too busy to handle new requests. The user gets
> > > impatient, and hits stop and then refresh a couple of times. This
fires
> up
> > > some new requests, but since they are from the same session as the
first
> > > request, they will execute on the thread that is still busy executing
> that
> > > first request. You'll see the number of ASP requests queued go up each
> > time
> > > the user hits refresh.
> > >
> > > When the first request finally finishes executing, the rest of the
> > requests
> > > will have their chance to execute and will leave the queue.
> > >
> > > Does that make sense?
> > >
> > > -Lisa
> > >
> > > > I'm having a problem with server too busy conditions, and I found a
> > > strange
> > > > behavior watching IIS process the page requests.
> > > >
> > > > Using IISTracer (http://www.pstruh.cz/help/iistrace) to analyze
which
> > > pages
> > > > IIS is processing at a moment I can see frequently why the asp
> requests
> > > > queue raises and goes down so frequently (from zero up to 50
requests,
> > and
> > > > then to zero in less then 30 seconds).
> > > >
> > > > Almost all the time this behavior happens because of multiple
requests
> > > being
> > > > kept in the queue from the same user, for the same page (I can see
> what
> > > page
> > > > is being requested and other parameters, like session cookies, that
> can
> > > > identify the user).
> > > >
> > > > Sometimes there are more than 10 requests like that for one user,
and
> > they
> > > > stay in the queue until one of them is served.
> > > >
> > > > At this time this page, and all the "clone" requests, is taken out
of
> > the
> > > > queue.
> > > >
> > > > I can see this happening in the IISTracer page and in the
performance
> > > > graphics for the ASP object.
> > > >
> > > >
> > > >
> > > > Anyone knows why this is happening?
> > >
> > > -----
> > > This posting is provided "AS IS" with no warranties, and confers
> > > no rights. You assume all risk for your use.
> > > © 2003 Microsoft Corporation. All rights reserved.
> > >
> >
> >
> >
>
> -----
> This posting is provided "AS IS" with no warranties, and confers
> no rights. You assume all risk for your use.
> © 2003 Microsoft Corporation. All rights reserved.
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: Multiple requests for the same page from the same user are.. |
|
| Back to top |
|
| |
| Related Topics: | | After moving web page - After moving a web page to different folder and making a new virtual directory on same machine with same IP address, users cannot connect to web site without deleting cache of internet files, cookies and all offline content. How can the server be set... |
|
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
