|
|
發表於 2017-6-1 09:10:15
|
顯示全部樓層
找到出處了
google ff382715
---
Hard faults are also known as page faults. Despite the negative connotation of the name, this is not an error condition. Rather, it represents an instance where a block of memory needed by the operating system or an application has to be fetched from the page file on the hard disk instead of from physical memory. A consistently high number of hard faults per second indicates a large—perhaps excessive—reliance on virtual memory, with consequent adverse performance effects.
The best way to gauge the adequacy of your currently installed RAM is to keep an eye on the Memory graph in Resource Monitor.The green portion of the bar indicates the percentage of your physical memory that’s currently in use; shades of blue indicate cached memory that is available on demand (Standby). It’s also important to watch the green line on the graphs to the right, which indicates the number of hard faults per second your system is generating. If you see it spike off the top of the graph for extended periods of time, you’ll want to take a closer look at how memory is being used.
Pay special attention to these numbers when you’re asking the most of your computer—you might even consider performing a stress test by successively opening the applications you use most often. Switch between programs, open and edit some data files, browse a couple dozen Web pages, and generally try to use more system resources than you would use at one time under normal circumstances. If you find yourself bumping up against the ceiling regularly, you might get a noticeable performance boost from additional RAM.
Do not get hung up on percentages. If you routinely hit a maximum of 85 per¬cent memory usage on a machine running 64-bit Windows 7 with 6 GB of physical RAM, you have 900 MB of free RAM, which is plenty of headroom. |
|
/1 
樓主
n_118|