Hi, You would run your component with a profiler, e.g. OptimizeIt. You would it run it a few times with normal logging, and record memory usage and CPU time statistics. Then you would run it with no logging at all (have a global static variable called LOGGING_TEST_MODE or whatever, have all the logging statements surrounded by if(LOGGING_TEST_MODE) ...), again record memory usage and CPU time statistics.
All of this can be automated with a test tool e.g. WinRunner / LoadRunner (big, fancy, expensive, but does a lot) or JMeter (free ;)). Or even wget, which is really nice and simple. Depends on your needs. In general, I would say that if you use logging carefully (you don't have a logging statement every two lines of code, but you do have them where needed and at the appropriate levels), and you take advantage of performance-oriented features e.g. using logger.isDebugEnabled() around logger.debug() statements, then the performance of log4j is going to be excellent. You really wouldn't need to worry about it too much. Tuning your own app is typically where more work is required... Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Arun Jannela [mailto:[EMAIL PROTECTED]] >Sent: Thursday, August 22, 2002 1:36 AM >To: 'Log4J Users List' >Subject: Log4J performance measuring > > > >How Log4J affects the performance? How to Test the component with and >without logging. How can I Collect the metrics? > >Regards, >Arun
This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you.
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
