For each application pool loaded into memory, a separate instance of the worker process exists.
To understand individual process behavior, you need to be concerned with two important memory
counters: (1) the private bytes value (2) the virtual bytes value.
The private bytes value tells you how much memory the process is using in physical RAM, which is an indication of how much pressure the process is putting on the system for memory. This value is the process footprint.
The virtual bytes value is the complete size of the addresses that the process has asked for, including both memory in physical RAM and virtual memory. This value is the key item for 32-bit processes because SharePoint can allocate only 2GB of virtual bytes before it runs out of memory—or more precisely, before it runs out of addresses for memory.
In general, using virtual memory on disk is a bad idea.
The counters that you can get from the Reliability and Performance Monitor are available as a set of
properties on the System.Diagnostics.Process class. These values allow you to monitor the memory usage of a .NET process while it’s running.
The information in Performance Monitor (and Data Collection Sets) is broken into a hierarchy that includes broad groupings called counters, individual metrics called objects, and instances, which represent the individual copies of the counters that capture and display information. A counter is a category such as processor, memory, process, and physical disk.
To understand individual process behavior, you need to be concerned with two important memory
counters: (1) the private bytes value (2) the virtual bytes value.
The private bytes value tells you how much memory the process is using in physical RAM, which is an indication of how much pressure the process is putting on the system for memory. This value is the process footprint.
The virtual bytes value is the complete size of the addresses that the process has asked for, including both memory in physical RAM and virtual memory. This value is the key item for 32-bit processes because SharePoint can allocate only 2GB of virtual bytes before it runs out of memory—or more precisely, before it runs out of addresses for memory.
In general, using virtual memory on disk is a bad idea.
The counters that you can get from the Reliability and Performance Monitor are available as a set of
properties on the System.Diagnostics.Process class. These values allow you to monitor the memory usage of a .NET process while it’s running.
The information in Performance Monitor (and Data Collection Sets) is broken into a hierarchy that includes broad groupings called counters, individual metrics called objects, and instances, which represent the individual copies of the counters that capture and display information. A counter is a category such as processor, memory, process, and physical disk.
No comments:
Post a Comment