Link Details

Link 1038135 thumbnail
User 376711 avatar

By grabnerandi
Published: Sep 25 2013 / 01:54

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
  • 12
  • 0
  • 648
  • 634

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.

Voters For This Link (11)

Voters Against This Link (0)

    Play Framework
    Written by: Ryan Knight
    Featured Refcardz: Top Refcardz:
    1. Akka
    2. Design Patterns
    3. OO JS
    4. Cont. Delivery
    5. HTML5 Mobile
    1. Akka
    2. JUnit/EasyMock
    3. Java Performance
    4. REST
    5. Java