Link Details

The potential overhead and performance impact of log outputs is widely known. In this new case we came across a severe response time impact on WebSphere caused by incorrect usage of a global shared logging service. Developers used their own Logger classes with no intention to actually logging out verbose output to disk. Due to the globally synchronized activity log in WebSphere this log output caused up to 99% overhead due to synchronization. Check out this blog and learn how to avoid these problems

Posted by grabnerandi  |   Sep 25 2013 / 01:54

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Recommended Links

Written by: Ryan Knight
Featured Refcardz: Top Refcardz:
  1. Apache Hadoop
  2. Play
  3. Akka
  4. Debugging JavaScript
  5. Design Patterns
  1. Apache Hadoop
  2. REST
  3. Java
  4. Git
  5. Java Performance
Connect with DZone