Windows Service (Physical memory)

[Jack]

I wrote a test windows service in VB.NET. All it does is
instantiate a class (test class with just a Name
property) and set it's Name property on OnStart.
I installed the service using installutil.exe and start
the service and look it up in the Task Manager. It uses
about 7600 K of memory. (priority is normal)

Question:
Why is the memory footprint so high?

(compared to all other services that are much much lower)

 

[Jerry Ham]

the other services are written in C or C++ and don't have the overhead
associated with the CLR.

 

[Herfried K. Wagner [MVP]]

I wrote a test windows service in VB.NET. All it does is
instantiate a class (test class with just a Name
property) and set it's Name property on OnStart.
I installed the service using installutil.exe and start
the service and look it up in the Task Manager. It uses
about 7600 K of memory. (priority is normal)

Question:
Why is the memory footprint so high?

The Service is implemented in .NET, so it will require the CLR and some
huge libraries. You shouldn't worry too much about that.

;-)