Folks,
I notice that when I do two concurrent processes (like ANALYZE.FILE from one
window and SELECT from another window) on the same large (3GB,64-bit) file,
the 'Pages/sec' count in Win2K3 goes through the roof, even though the
'memory commit charge' is only 176MB out of 2465MB.
Maybe the 'Pages/sec' count is not measuring what I expect it to, but it
seems odd to me for the system to be paging (i.e. swapping program code
segments in and out of memory) in this situation. I'd except the disk
system to be getting a thrashing as the two processes want to read different
bits of the same file, but not paging.
Can anyone tell me
1) Do I understand correctly what is happening?
If not, what _is_ going on?
2) Are there any UV configuration tunables which could
improve the situation? If so, which one(s)?
3) Are there any Windows configuration tunables which
could improve the situation? If so, which one(s)?
Oh, it's UV 10.0.15, but I don't think that's terribly relevant
Thanks
Mike
The information contained in this Internet Email message is intended
for the addressee only and may contain privileged information, but not
necessarily the official views or opinions of the New Zealand Defence Force.
If you are not the intended recipient you must not use, disclose, copy or
distribute this message or the information in it.
If you have received this message in error, please Email or telephone
the sender immediately.
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
