One last question about ASP.NET 1.1 application recycling, load time and other boring stuff

[Ravi Ambros Wallau]

Dear friends:
This is my third question on this news in three days... Sorry for this
spam behavior
I've a lot of problems on "first page load" after some change on
web.config or even in the contents of bin folder...
Nathan Sokalski passed me a link to ILMerge library, I've made some
tests grouping a set of DLL's that are loaded without reflection, but there
were no improvements on load time.
I've noted that ASP.NET copies all assemblies that are on bin folder to
the Temporary ASP.NET Files, located on Framework folder under Windows
folder. I don't know why ASP.NET does that, but whatever, I think that this
behavior cannot be modified.
My question is: When using ASP.NET 1.1, is there some automatic
recycling behavior? My pages are not changed often. But we have the
impression that, once or twice in a day, the time took to load a page is
heavily increased, even if this page has no great processing on this
operation... Am I missing something? ASP.NET does this for any reason?

Thanks,

 

[Nicholas Paldino [.NET/C# MVP]]

Ravi,

You pointed it out yourself.

If you make a change to the web.config file, the contents of the bin
folder, or the ASPX pages in your application, ASP.NET will recylce your
app, causing a new application domain to be created and runing the app in
that, recompiling the ASPX files (if necessary, I believe).

This is the delay that you are seeing on the first page request. There
is no way around this behavior, as ASP.NET does this to ensure the integrity
of the app.

Hope this helps.

 

[Ravi Ambros Wallau]

Hi, Nicholas,
I'm aware of such behavior. Clarifying, may the application be recycled
in Windows 2000 server without any changes, and without any IIS restaring?
Thanks,
Ravi.

Ravi,

You pointed it out yourself.

If you make a change to the web.config file, the contents of the bin
folder, or the ASPX pages in your application, ASP.NET will recylce your
app, causing a new application domain to be created and runing the app in
that, recompiling the ASPX files (if necessary, I believe).

This is the delay that you are seeing on the first page request. There
is no way around this behavior, as ASP.NET does this to ensure the
integrity of the app.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Dear friends:
This is my third question on this news in three days... Sorry for this
spam behavior
I've a lot of problems on "first page load" after some change on
web.config or even in the contents of bin folder...
Nathan Sokalski passed me a link to ILMerge library, I've made some
tests grouping a set of DLL's that are loaded without reflection, but
there were no improvements on load time.
I've noted that ASP.NET copies all assemblies that are on bin folder
to the Temporary ASP.NET Files, located on Framework folder under Windows
folder. I don't know why ASP.NET does that, but whatever, I think that
this behavior cannot be modified.
My question is: When using ASP.NET 1.1, is there some automatic
recycling behavior? My pages are not changed often. But we have the
impression that, once or twice in a day, the time took to load a page is
heavily increased, even if this page has no great processing on this
operation... Am I missing something? ASP.NET does this for any reason?

Thanks,

 

[Nicholas Paldino [.NET/C# MVP]]

Ravi,

Generally, no, it shouldn't. The only things I can think of would be is
that the memory consumption grew too large and as a result, and ASP.NET
recycled the app domain as a result.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Hi, Nicholas,
I'm aware of such behavior. Clarifying, may the application be recycled
in Windows 2000 server without any changes, and without any IIS restaring?
Thanks,
Ravi.

Ravi,

You pointed it out yourself.

If you make a change to the web.config file, the contents of the bin
folder, or the ASPX pages in your application, ASP.NET will recylce your
app, causing a new application domain to be created and runing the app in
that, recompiling the ASPX files (if necessary, I believe).

This is the delay that you are seeing on the first page request.
There is no way around this behavior, as ASP.NET does this to ensure the
integrity of the app.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Dear friends:
This is my third question on this news in three days... Sorry for
this spam behavior
I've a lot of problems on "first page load" after some change on
web.config or even in the contents of bin folder...
Nathan Sokalski passed me a link to ILMerge library, I've made some
tests grouping a set of DLL's that are loaded without reflection, but
there were no improvements on load time.
I've noted that ASP.NET copies all assemblies that are on bin folder
to the Temporary ASP.NET Files, located on Framework folder under
Windows folder. I don't know why ASP.NET does that, but whatever, I
think that this behavior cannot be modified.
My question is: When using ASP.NET 1.1, is there some automatic
recycling behavior? My pages are not changed often. But we have the
impression that, once or twice in a day, the time took to load a page is
heavily increased, even if this page has no great processing on this
operation... Am I missing something? ASP.NET does this for any reason?

Thanks,

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

Ravi,

You pointed it out yourself.

If you make a change to the web.config file, the contents of the bin
folder, or the ASPX pages in your application,

If you make a change in the aspx file it will not recicle the app. this
pages are dynamically parsed.

 

[Scott C]

Ravi,

Generally, no, it shouldn't. The only things I can think of would be is
that the memory consumption grew too large and as a result, and ASP.NET
recycled the app domain as a result.

I remember someone a *long* time ago made the comment about virus
checkers "touching" the files and causing the app to be recycled.

Just a lead, anyway.

Scott