Re: Newbie: Log4Net or MS Logging Application Block?

[Mike Liddell]

Hi, it was just my back of the envelope guess at total working set usage when I was considering the one-static-logger-per-code-class approach, which was new to me at the time. this was my thinking... 10K code classes is definitely an upper limit, and 100-1000 is probably the common range.  I might also have some non-code-class loggers and so I assumed that 10K in-memory logger instances is a reasonable upper limit.  I haven't yet determined how big a log4net logger instance is, but I though 100bytes for the string name and some ancillary items, with references into a common hierarchy object that I presume isn't particularly heavy for consumption.  I couldn't quickly think of a way to determine the byte-count of of per-logger-instance data, and/or the per-application data.  On these number I figured that at most 1MB would be devoted to log4net data in a big app, which is totally fine. Does anyone have some hard data - should I worry about memory footprint? regards, Mike. Walden H. Leverich wrote: > I personally have my own wrapper object that includes a Logger instance and I create a >static one of those per code class.  I am budgeting about 100bytes per instance at, say, >10K classes max for 1MB working set usage. I'm not sure if this is accurate.   I assume you mean 10K instances, not 10K classes, that would be one hell of a class library. J   Assuming it is indeed instances then why are you counting bytes per instance? What instance data are you storing? We’ve gone with the one logger instance per class via a static logger and since it’s static it would not add any storage to the instance, right? What am I missing?   -Walden   -- Walden H Leverich III Tech Software (516) 627-3800 x3051 [EMAIL PROTECTED] http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.)