Manish,
From what I remember, I believe the recommendation is to have something
go through and view the pages so that they get compiled. From the section
of the .NET framework titled "Developing High-Performance ASP.NET
Applications":
If you have a large Web application, consider performing pre-batch
compilation. Batch compilation is performed whenever a first request is made
to a directory. If no page in the directory has been parsed and compiled,
this feature will parse and compile all pages in the directory in chunks to
provide better disk and memory usage. If this takes too long, a single page
will be parsed and compiled quickly so that the request can be processed.
This feature gives ASP.NET a performance benefit, since it compiles many
pages into a single assembly. Accessing a page from an assembly that is
already loaded is faster than loading a new assembly per page.
The downside of batch compilation is that if the server receives many
requests for pages that have not been compiled, performance can be poor
while the Web server parses and compiles them. To solve this problem, you
can perform pre-batch compilation. To do so, before your application goes
live, simply request a page from it — it does not matter which page. Then,
when users first access your site, the pages and their assembly will already
be compiled.
There is no easy mechanism to tell when batch compilation occurs. Wait until
the CPU idles or no more compiler processes, such as csc.exe (the C#
compiler) or vbc.exe (the Visual Basic compiler), are being launched.
Also try to avoid changing assemblies in the \bin directories for your
applications. Changing a page will cause a reparse and compilation of that
single page, but replacing an assembly in a \bin directory will cause a
whole new batch compile of that directory.
On larger scale sites with many pages, it may be better to design your
directory structure differently based on how often you plan to replace pages
or assemblies. Pages that will be changed infrequently could be stored in
the same directory and pre-batch compiled at specific times. Pages that
change more frequently should be in their own directories (a few hundred
pages at most in each) for fast compiles.
A Web application may contain many subdirectories. Batch compilation occurs
at the directory level, not the application level.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
-
ni**************@exisconsulting.com
"Manish Jain" <ma******@hotmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Environment: Windows 2000 Server (SP4), ASP.Net/C# (Framework 1.1)
Hardware: PIII @ 700 MHz, 512 MB RAM
--------------------------------------------------------------------------
-- -------------------------------------------------------
I have developed a web application which I am deploying on above mentioned
environment. Problem is that when I run it for the first time after a
Build, then there is too much of CPU hogging. The Task Manager shows
aspnet_wp.exe and csc.exe as the culprits. This happens for each page, for the first
time.
My understanding is that c-sharp compiler compiles the aspx pages the
first time. Subsequently, this overhead is not required till the next build.
Can somebody explain the reason behind the slow performance?
Is there any configuration/setting that I am ignoring?
Is it possible to do what csc.exe does at build time?
Basically, is there something that I can do to ensure less load time for
the first time. I am facing very low performace on my intranet, i am worried
about what would happen on the Internet.
Thanks and Regards
Manish
