Assemblies Working Set

[Nando]

Hi

I developed a layered desktop application. Data, business, and presentation
layers, all of them built a single assembly (the main .EXE), with a working
set of about 4.5MB. Then I was needed that the reports of the application
were available on the web so I splited the assembly into the presentation
layer (.EXE) and the business and Data layers built into a another assembly
(.DLL) so a web page can be built around it!.

To my surprise the working set for the WinForm application went from 4.5MB
to 12MB! with no additions to the code whatsoever!

Having the code splitted is responsible for this? keeping as few assemblies
as possible is a way to reduce the working set?

Thanks in advance

 

[Michael Giagnocavo [MVP]]

There will be some overhead from multiple assemblies. However, I'm surprised
you ever got a WinForm that does anything with only 4.5MB to begin with.
Search around on Google [Groups] for .NET memory usage / management. How are
you measuring the usage?

 

[Nando]

Hi, Michael

Thanks In advance.

I have to admit that I made a mistake about the working set of the
application. I repeated the experience and then I realized that the 4.5MB
working set I reported was when the application was minimized. (DUH!!! )

By the way do you know is that it happens?

Atte:
Nando

PD: The figured I showed are as reported by the TaskManager.