Discussions

Blogs: Log4J a Potential Performance Hit.

Bookmark and Share Get thread feed

  1. Log4J a Potential Performance Hit. (2 messages)

    If you’ve ever wondered how log4j injects the line numbers of the code generating the debugging information then now you need look no farther then Zarar latest blog entry. In his blog Zarar not only explains how log4j achieves this he also points out that you may want to take care to ensure this feature is turned off in production.
    Reply to this

    Threaded Messages (2)

  2. Who knew?[ Go to top ]

    Yes, everyone should read the documentation
    .

    Used to output the line number from where the logging request was issued.

    WARNING Generating caller location information is extremely slow. It's use should be avoided unless execution speed is not an issue.
    Reply to this Reply to original

  3. JXInsight CallStack Benchmark Insight Article[ Go to top ]

    Hi,

    The Java/J*EE Performance Management Insight Article series on our website (http://www.jinspired.com) discusses the cost of this call and compares it with JXInsight's Tracer implementation.

    http://www.jinspired.com/products/jdbinsight/callstackbenchmark.html

    Regards,

    William Louth
    JXInsight Product Architect
    JInspired

    "J*EE tuning, testing and tracing with JXInsight"
    http://www.jinspired.com
    Reply to this Reply to original