Quote:
Originally Posted by jarod
I read and understand roughly 90% what you are saying but then after doing some research on other sources, they claim that you can also see the Peak commit charge compared to your total physical memory. If the peak is close or over the total physical, then it is time to upgrade memory. But your way seems to be a longer and more complicated one
|
What you have to remember is that not all your physical memory is available for applications. Windows reserves some of it for other purposes. Available memory is the point at which Windows switches to virtual (PageFile) memory.
Quote:
|
Also in the commit table, limit meaning the maximum memory that the system can go (both physical and paging). Is that right?
|
That's correct.
Quote:
What is the relation here, total commit charge is total memory usage (both physical and paging) whereelse, available in physical column is remaining physical memory at that moment. So how could we use this relation to determine what memory we need to upgrade. Why can't i just increase paging to replace the additional memory that i need
Thanks
|
Total commit charge is what you are actually using, whereas Peak is the maximum that you used during the present session. The important thing is that whilst you can use virtual memory for occasional peaks, if you are continually using virtual memory under normal usage your machine will be slower than if you were using physical memory, as physical memory is much faster than virtual memory. Using virtual memory also increases the wear on your hard drive. It may also mean that your system cache is not being used and that further slows the system down.