Hi Paul,
Yes, we are using IIS 6.0. I have also thought about the
application pool. I will have them make sure that this is
not restarted, and see if it makes any difference.
But i doubt that this is the problem. When i requested the
page this morning, it was slow on my first request, but
only 6 minutes before my request someone else had
requested an aspx-page (looking in the IIS log). And if i
remember correctly, when the application pool recycles, it
writes the headers into the log file(#fields, #date and so
on), and this is not true between these two requests.
So if you have any other ideas, they are welcome :-)
Thank you!
[quoted text, click to view] >-----Original Message-----
>If you are running on Windows2003/IIS6, the default
setting for the default
>application pool is to recycle the app pool if the app is
idle for a certain
>period. This can cause a recompilation to occur and/or
everything to be
>re-cached so it would slow down again until its all back
in the cache. If
>this is the case, (IIS6/Win2k3) then go into the IIS
manager, right click on
>the default app pool (or whichever app pool your web
application is in, and
>examine some of those settings. Perhaps try disabling
this or extending this
>to see if it makes a difference.
>
>--
>
>- Paul Glavich
>ASP.NET MVP
>ASPInsider (
www.aspinsiders.com)
>
>
>"Tom" <anonymous@discussions.microsoft.com> wrote in
message
>news:03a801c4f7b2$81fd5880$a601280a@phx.gbl...
>> Any ideas what can cause ASP.NET pages to be slow now
and
>> then? It can take more than 5 seconds to get the page,
>> which is way to much. One of the pages (not sure how
many
>> there are, i have just noticed it on the "home" page)
are
>> very simple (only HTML, no database or anything
involved).
>>
>> I have made sure that i have cached the page:
>> <%@ OutputCache Duration="7200" VaryByParam="none"%>
>>
>> I don't think i have ever seen the slowness when i am
>> navigating on the website (does this mean anything?)
>>
>> I'm trying to figure out if it can be my code, or the
>> webserver being too busy (i don't have control over the
>> webserver)
>>
>> Thank you!
>>
>
>
>.