B
Bob
I have a graphic application that runs rather slowly. When I look at
the performance stats, I see that it is encountering what appear to
be a large number of page faults:
Mem usage: 74K-K
VM Size 60K-K
Page Faults: 48K
I/O Reads: 11K
I/O Bytes 34M
The system has 384MB of physical Ram, and it has over 200mb available
at any given time. So, why all the paging ? Shouldn't this application
be able to keep itself in memory and avoid all the paging? Or is Win2K
paging measuring something other than what I think ? Is there any way
to tune the system to allow this application to take more memory ?
(I've fooled with priority already, that was not a good thing to do).
Thanks,
the performance stats, I see that it is encountering what appear to
be a large number of page faults:
Mem usage: 74K-K
VM Size 60K-K
Page Faults: 48K
I/O Reads: 11K
I/O Bytes 34M
The system has 384MB of physical Ram, and it has over 200mb available
at any given time. So, why all the paging ? Shouldn't this application
be able to keep itself in memory and avoid all the paging? Or is Win2K
paging measuring something other than what I think ? Is there any way
to tune the system to allow this application to take more memory ?
(I've fooled with priority already, that was not a good thing to do).
Thanks,