Posted by member 7 on 2003-08-29 11:08:21 link
Egonz: not really.
Be very careful with those numbers. Don't trust task manager. :P
For example, if you link to a 20 MB DLL it is mapped into your app's memory. That means task manager adds the 20 MB in the memory usage column, even if you use zero function from the DLL so it's not even loaded into the RAM. If you leave your app running for a while and launch other programs in the meantime you'll see the memory usage decrease (in task manager). For example, on my win2k setup task manager says LS uses about 6 MB right after login. At the moment (ie. a few hours later) it says 3 MB. Same with the "virtual memory usage" column, so it doesn't just move the numbers from one column to the other. =)
It's very hard to determine the "real" memory usage. I don't know if there even is a proper way. What would you do for example if you have a DLL that is used by two programs? Add it to both? Just to one? If so, to which one, and why?
Be very careful with those numbers. Don't trust task manager. :P
For example, if you link to a 20 MB DLL it is mapped into your app's memory. That means task manager adds the 20 MB in the memory usage column, even if you use zero function from the DLL so it's not even loaded into the RAM. If you leave your app running for a while and launch other programs in the meantime you'll see the memory usage decrease (in task manager). For example, on my win2k setup task manager says LS uses about 6 MB right after login. At the moment (ie. a few hours later) it says 3 MB. Same with the "virtual memory usage" column, so it doesn't just move the numbers from one column to the other. =)
It's very hard to determine the "real" memory usage. I don't know if there even is a proper way. What would you do for example if you have a DLL that is used by two programs? Add it to both? Just to one? If so, to which one, and why?