Quote:
Originally Posted by JohnthePilot
Limit shows what is available and Peak shows the maximum that has been reached during this session. If Peak approaches Limit, then you need to consider increasing memory. Whether this is physical or virtual depends on the other table. Available shows how much physical memory can be used before switching to virtual memory. If the Total in Commit Charge is much greater than Available, then you should consider increasing your physical memory, otherwise you can increase your virtual memory. To sum up, the more physical memory you have the better.
|
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
Also in the commit table, limit meaning the maximum memory that the system can go (both physical and paging). Is that right
Quote:
Originally Posted by JohnthePilot
If the Total in Commit Charge is much greater than Available, then you should consider increasing your physical memory, otherwise you can increase your virtual memory. To sum up, the more physical memory you have the better.
|
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