Hi everyone,

I have observed that the ngen process appears in the list of processes
in
taskmgr while .net framework 1.1 gets installed. This process consumes
0-50%
of cpu and 0-20K of RAM.
I would like to know if this process can be a cause of slowing down
performance of a high speed application. The installer of this
application
examines whether .net framework is installed, if it is not installed it
first
installs .net 1.1 and then continues with its own installation.
It would be great if anyone knows about problems related to ngen during

installation of .net framework 1.1, say, under low memory conditions,
or for
particular OSs, or for particular hardware configuration
--

--
Thanks,
Sameeksha
MCAD.Net

I noticed the same high-impact process during install of the 2.0
framework. A field install of the 2.0 framework on client machines --
two of which were quite slow and old hardware -- certainly brought them
to their knees and was slow as the itch. On their server, no
interruption of service was observed, but it was a small network with
less than 20 users.

I would definitely try to install the framework on a server during off
hours or downtime.

--Bob

Sameeksha wrote:

Thanks, Bob.
So we are in a position to say that the ngen process which runs during
install of .net framework is probably the reason of slow performance of
installation. Could you throw any light on the workarounds for this problem?
--
Thanks,
Sameeksha
MCAD.Net


"Bob Grommes" wrote:

We are in a position to say that it's our impression that this may be
significant, but I certainly haven't come anywhere close to determining
that in a definitive manner.

Unless someone has an alternative MSI for installing the framework on
offer, no I have no idea what you can do about it other than put "faster
framework installs" on MSFT's wish line.

Best,

--Bob

Sameeksha wrote: