andrew goodman said:
Thanks for the info. Is there a way to lower the priority? Response time
for both foreground processes and other services fell through the floor.
I
had to uninstall .net 2.0 to get responsiveness back.
:
The service should only run during idle time, that means when no messages
are posted to the windows queues, and it should only run for a short period
of time needed to optimize the framework libraries.
Did you check how long it was running after v2.0 install?
Note that you can always disable the service or better pause the
optimization service by means of the "ngen queue pause" command line
command.
You can also check the status of the queue by running "ngen queue status".
Willy.