V
Villy Madsen
Greetings
I have an application (an VAX emulator) that opens two Gbyte sized files.
The first time that I run this program in a windows (XP/HOME SP2 - same
thing happens on an XP/Prof SP2 on a laptop and another desktop (every
system I've tried it on) also all are NTFS)
Task Manager shows a lot of paging activity for the process and lots of IO.
The amount of virtual memory allocated stays the same, the amount of
physical memory in use stays more or less the same, but the page fault and
write IO start climbing - until the IO bytes written looks suspicially like
the total size of the two files being opened. Read IO is a tiny fraction
(in terms of IOs and bytes) of the write IO.
If I shut the process down and restart it - it doesn't happen.
If I were a guessing kind of person, I would guess that WXP is creating an
area in the paging file to hold these files
Any thoughts on how I can stop this from happening - you wouldn't believe
how long it takes on the laptop.
Villy
I have an application (an VAX emulator) that opens two Gbyte sized files.
The first time that I run this program in a windows (XP/HOME SP2 - same
thing happens on an XP/Prof SP2 on a laptop and another desktop (every
system I've tried it on) also all are NTFS)
Task Manager shows a lot of paging activity for the process and lots of IO.
The amount of virtual memory allocated stays the same, the amount of
physical memory in use stays more or less the same, but the page fault and
write IO start climbing - until the IO bytes written looks suspicially like
the total size of the two files being opened. Read IO is a tiny fraction
(in terms of IOs and bytes) of the write IO.
If I shut the process down and restart it - it doesn't happen.
If I were a guessing kind of person, I would guess that WXP is creating an
area in the paging file to hold these files
Any thoughts on how I can stop this from happening - you wouldn't believe
how long it takes on the laptop.
Villy