Performance

[arndt.blumenthal]

Hi,

i implement a ASP.NET-Application for a customer. Every
day the customer has the problem, that the first access
to the application takes very long.
What could be the reason?

Thanks for help

Arndt

 

[Jim Cheshire [MSFT]]

Arndt,

Is it possible that the customer has some kind of process indexing the
folders each night or something? If so, it would cause a Change Notify
which would cause a recycle of the app domain and a JIT compile upon first
browse.

Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------

 

[Kevin Spencer]

An ASP.Net web application stops 20 minutes after the last request for a
page happens. The next page request must restart the application. This is
most probably what your customer is experiencing.

--
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

 

[Jim Cheshire [MSFT]]

Kevin,

This would indeed cause the Application_Start event to fire and the app
domain to reload, but that process should be unnoticeable to the user
unless the worker process has gone down (which it shouldn't). A delay in
execution on first browse is almost always caused by JITing.

Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------

 

[Kevin Spencer]

This would indeed cause the Application_Start event to fire and the app

domain to reload, but that process should be unnoticeable to the user
unless the worker process has gone down (which it shouldn't). A delay in
execution on first browse is almost always caused by JITing.

....which would be the cause in the case I mentioned if, for example, the
developer didn't compile DLLs.

--
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

Kevin,

This would indeed cause the Application_Start event to fire and the app
domain to reload, but that process should be unnoticeable to the user
unless the worker process has gone down (which it shouldn't). A delay in
execution on first browse is almost always caused by JITing.

Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------

From: "Kevin Spencer" <[email protected]>
References: <[email protected]>
Subject: Re: Performance
Date: Fri, 21 Nov 2003 07:55:06 -0500
Lines: 25
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.3790.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Message-ID: <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: dynamicsystems.com 216.54.1.213
Path:

cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGXA06.phx.gbl!TK2MSFTNGXA0

5.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
Xref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.framework.aspnet:191822
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

An ASP.Net web application stops 20 minutes after the last request for a
page happens. The next page request must restart the application. This is
most probably what your customer is experiencing.

--
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

in message news:[email protected]...

 

[Jim Cheshire [MSFT]]

Kevin,

Even if you are using inline script and relying on compile at first browse,
a recycling of the process or unloading of app domain will not cause the
application to be recompiled. Only a CHANGE NOTIFY will cause that.

Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------

From: "Kevin Spencer" <[email protected]>
References: <[email protected]>

Subject: Re: Performance
Date: Fri, 21 Nov 2003 09:16:18 -0500
Lines: 82
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.3790.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Message-ID: <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: dynamicsystems.com 216.54.1.213
Path: cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08
..phx.gbl!TK2MSFTNGP11.phx.gbl
Xref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.framework.aspnet:191845
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

This would indeed cause the Application_Start event to fire and the app
domain to reload, but that process should be unnoticeable to the user
unless the worker process has gone down (which it shouldn't). A delay in
execution on first browse is almost always caused by JITing.

...which would be the cause in the case I mentioned if, for example, the
developer didn't compile DLLs.

--
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

Kevin,

This would indeed cause the Application_Start event to fire and the app
domain to reload, but that process should be unnoticeable to the user
unless the worker process has gone down (which it shouldn't). A delay in
execution on first browse is almost always caused by JITing.

Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------

From: "Kevin Spencer" <[email protected]>
References: <[email protected]>
Subject: Re: Performance
Date: Fri, 21 Nov 2003 07:55:06 -0500
Lines: 25
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.3790.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Message-ID: <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: dynamicsystems.com 216.54.1.213
Path:

cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGXA06.phx.gbl!TK2MSFTNGXA 0

5.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
Xref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.framework.aspnet:191822
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

An ASP.Net web application stops 20 minutes after the last request for a
page happens. The next page request must restart the application. This is
most probably what your customer is experiencing.

--
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

in message Hi,

i implement a ASP.NET-Application for a customer. Every
day the customer has the problem, that the first access
to the application takes very long.
What could be the reason?

Thanks for help

Arndt

 

[Kevin Spencer]

Thanks Jim. I'll file that with the other 25 new things I learned today! ;-)

--
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

Kevin,

Even if you are using inline script and relying on compile at first browse,
a recycling of the process or unloading of app domain will not cause the
application to be recompiled. Only a CHANGE NOTIFY will cause that.

Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------

From: "Kevin Spencer" <[email protected]>
References: <[email protected]>

Subject: Re: Performance
Date: Fri, 21 Nov 2003 09:16:18 -0500
Lines: 82
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.3790.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Message-ID: <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: dynamicsystems.com 216.54.1.213
Path:

cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08

phx.gbl!TK2MSFTNGP11.phx.gbl
Xref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.framework.aspnet:191845
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

This would indeed cause the Application_Start event to fire and the app
domain to reload, but that process should be unnoticeable to the user
unless the worker process has gone down (which it shouldn't). A delay in
execution on first browse is almost always caused by JITing.

...which would be the cause in the case I mentioned if, for example, the
developer didn't compile DLLs.

--
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

Kevin,

This would indeed cause the Application_Start event to fire and the app
domain to reload, but that process should be unnoticeable to the user
unless the worker process has gone down (which it shouldn't). A delay in
execution on first browse is almost always caused by JITing.

Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
From: "Kevin Spencer" <[email protected]>
References: <[email protected]>
Subject: Re: Performance
Date: Fri, 21 Nov 2003 07:55:06 -0500
Lines: 25
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.3790.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Message-ID: <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: dynamicsystems.com 216.54.1.213
Path:

cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGXA06.phx.gbl!TK2MSFTNGXA
0

5.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
Xref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.framework.aspnet:191822
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

An ASP.Net web application stops 20 minutes after the last request for a
page happens. The next page request must restart the application. This is
most probably what your customer is experiencing.

--
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

in message Hi,

i implement a ASP.NET-Application for a customer. Every
day the customer has the problem, that the first access
to the application takes very long.
What could be the reason?

Thanks for help

Arndt

 

[Jim Cheshire [MSFT]]

No problem. In case you're interested, what we do is create an XML file
that we derive from the name of the page that is compiled. (i.e.
Page.aspx.2d53e27.xml). That file contains an entry which has the full
path to a file that the page depends on. If any of those files change, the
temporary DLL is not used and the page is recompiled. Therefore, if the
page doesn't change, even if the app domain recycles, we still use the
temporary assembly UNLESS a special file is modified (such as a
configuration file or the global.asax).

If a special file is modified, the app domain is recycled and the app's
info in the temporary folder are deleted. To determine if a change has
occurred, we use a hash file named hash.web in the Temporary ASP.NET Files
folder for the app. That file contains a single hex number that is a hash
based on all of the special files except for the web.config files. When
the app domain is recyled, we recalculate that hex code and compare it with
the one in hash.web. If those two don't match, we know that something has
changed and we delete the contents of ASP.NET temp folder for the app and
recompile.

The whole thing is not as simple as many people might think. And now you
know the rest of the story.

Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------

From: "Kevin Spencer" <[email protected]>
References: <[email protected]>

<[email protected]>
<[email protected]>

Subject: Re: Performance
Date: Fri, 21 Nov 2003 14:42:56 -0500
Lines: 140
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.3790.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Message-ID: <#[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: dynamicsystems.com 216.54.1.213
Path: cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!cpmsftngxa08.phx.gbl!cpmsftngxa10.
phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
Xref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.framework.aspnet:191956
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

Thanks Jim. I'll file that with the other 25 new things I learned today! ;-)

--
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

Kevin,

Even if you are using inline script and relying on compile at first browse,
a recycling of the process or unloading of app domain will not cause the
application to be recompiled. Only a CHANGE NOTIFY will cause that.

Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------

From: "Kevin Spencer" <[email protected]>
References: <[email protected]>

Subject: Re: Performance
Date: Fri, 21 Nov 2003 09:16:18 -0500
Lines: 82
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.3790.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Message-ID: <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: dynamicsystems.com 216.54.1.213
Path:

cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP0 8

phx.gbl!TK2MSFTNGP11.phx.gbl
Xref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.framework.aspnet:191845
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

This would indeed cause the Application_Start event to fire and the app
domain to reload, but that process should be unnoticeable to the user
unless the worker process has gone down (which it shouldn't). A delay in
execution on first browse is almost always caused by JITing.

...which would be the cause in the case I mentioned if, for example, the
developer didn't compile DLLs.

--
Kevin Spencer
.Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

Kevin,

This would indeed cause the Application_Start event to fire and the app
domain to reload, but that process should be unnoticeable to the user
unless the worker process has gone down (which it shouldn't). A delay in
execution on first browse is almost always caused by JITing.

Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
From: "Kevin Spencer" <[email protected]>
References: <[email protected]>
Subject: Re: Performance
Date: Fri, 21 Nov 2003 07:55:06 -0500
Lines: 25
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.3790.0
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Message-ID: <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: dynamicsystems.com 216.54.1.213
Path:

cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGXA06.phx.gbl!TK2MSFTNGX A
0

5.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
Xref: cpmsftngxa07.phx.gbl
microsoft.public.dotnet.framework.aspnet:191822
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

An ASP.Net web application stops 20 minutes after the last request

for

a This
is