The author writes "With ASP.NET you can configure the 'ASP.NET engine' to automatically restart itself when certain criteria are met. For example, if the Web server has 100 requests queued up, you may wish to have the Web server restarted, assuming that some script or DLL is hanging the Web server. Additionally, you can set requirements on restarting the Web server on the memory usage, the total number of requests, or by the total time the Web server's run. This proactive approach was implemented by the ASP.NET team in order to increase the overall uptime of a Web site running ASP.NET: if the memory suddenly shoots through the roof, the Web server can be restarted, reigning in the memory usage and starting anew. The information regarding the life cycle of the current (and past) ASP.NET processes can be examined through the use of the ProcessModelInfo class." This article examines how to retrieve and present such information.