Re: Lot of classes


>Talking with another developer, he suggested me that I should not create a
>subclass for every Utility that I have, because every class has a big
>footprint and as my application has a lot of utilities, my overall resource
>usage will be dramatically high.

How many are "a lot"? Tens, hundreds, thousands?

I wouldn't worry about it unless you have actual profiling and memory
usage data that indicates it's a problem.


Now, if you want to reduce the memory footprint of your app, perhaps
you should consider a design where you don't have to load the plugin
assemblies until they are actually needed. Or will the user actually
use all "utilities"?


Mattias

--
Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.
.

Relevant Pages

  • Re: Objects allocated memory
    ... Seems like you'd want a #footprint method in every class that accumlated the memory footprint of the object. ... RMagick OS X Installer ... RMagick Installation FAQ ...
    (comp.lang.ruby)
  • Re: Lot of classes
    ... do you consider that implement this solution with subclass of Utility ... > I am writing an application that will handle plugins, ... The footprint from the classes themselves is likely to be ...
    (microsoft.public.dotnet.framework)
  • Re: OT: Who will switch to (or at least try out) Opera now that they have free registrations?
    ... memory footprint it doesn't make it quick. ... I do concede that small footprint probably means faster start up time tho:) ... > Mozilla suite, - browser, mail, calender, gives me all I need for a ... > small business setting. ...
    (Debian-User)