Working set memory dependent on exec name ???

[Hang Dog]

A colleague has been trying to reduce the memory footprint of a 32 bit
app running on vista 64 and has noticed some weird behaviour in the
reported size of the private working set.

He made some changes and recompiled the app. Then he ran the app and
loaded in a data file. The task manager reports that private working set
is 98Mb. He then simply renamed the app to 'fred.exe' now when he runs
fred.exe and loads the same data file the private working set is
reported to be 125Mb. Rename the file back to its original name, repeat
and the private working set is back to 98Mb.

Does anyone know what causes this?

 

[Bo Persson]

A colleague has been trying to reduce the memory footprint of a 32
bit app running on vista 64 and has noticed some weird behaviour in
the reported size of the private working set.

He made some changes and recompiled the app. Then he ran the app and
loaded in a data file. The task manager reports that private
working set is 98Mb. He then simply renamed the app to 'fred.exe'
now when he runs fred.exe and loads the same data file the private
working set is reported to be 125Mb. Rename the file back to its
original name, repeat and the private working set is back to 98Mb.

Does anyone know what causes this?

Task manager is notoriously unreliable in its reports.

The amount of memory a program is allowed to use also depends on the
amount of memory available in the machine. If no other programs
compete for the memory, why not let the program keep what's already
allocated?


Bo Persson