This makes no sense as long as you don't specify what memory space (what
memory perf. counter or taskman counter) you are talking about.
Also, .NET doesn't manage process memory, the CLR only manages it's private
heaps such as the GC heap(s). The process memory is managed by the OS memory
manager.
If you ever have seen a managed application that only takes 1-2 Mb (Working
set) it is because :
1. it is a minimized winforms app. or
2. the system is overloaded and the memory manager has started to trim all
processe's working sets. At this point the system starts thrashing and UI
style applications tend to freeze.
Willy.
"Etienne Boucher" <et*****@novat.qc.ca> wrote in message
news:Ov**************@TK2MSFTNGP14.phx.gbl...
Your program does not "use" 16Mb of ram. That amount is simply reserved by
.NET for faster memory management. If you fill up your RAM .NET will
switch to a more agressive memory management mode and the amount of memory
reported by the task manager will probably go down a lot, down to 1-2Mb
probably.
Etienne Boucher