Note: I assuming that Terminal Server shares dlls between sessions.I don't think it does... AFAIK, the sessions on a Terminal Server are completely separate and don't really reuse anything.
The best way to determine the extra physical ram consumed by an app is to note the Physical Memory Available (Performance tab of the Task Manager) when you've loaded one copy, start a second copy and note it again. That will give you the cost of each new copy which will be considerably less than the headline figure attributed to the app.Sounds reasonable ;o) I'll have a look at that number and see if the numbers look better. That's all a little hard to test without actually pushing an app out to the server and watching how it's doing.
For Win32::GUI apps, it comes out at around 3.5MB per copy on my system. Not trivial, but 30x3.5 is better than 30x6.9 :)Indeed ;o)
In reply to Re^2: Memory requirements for a Win32 GUI
by pvbcharon
in thread Memory requirements for a Win32 GUI
by pvbcharon
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |