IBM Support

PI88370: MEMORY BUFFER TRACE OUTPUT PERFORMANCE IS SLOW WHEN BASIC TRACE FORMAT IS USED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the trace output is set to Memory Buffer, with trace enable
    and the trace format set to Basic, the execution time is heavily
    spent on retrieving the LogRecordStack for each AsyncLogRecord.
    The retrieval of the LogRecordStack is only needed when the trac
    format is set to Advanced.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  Version 8.5.5 and 9.0, who enable the       *
    *                  Memory                                      *
    *                  Buffer trace output, with the trace format  *
    *                  set                                         *
    *                  to Basic.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: The performance of the Memory buffer    *
    *                      trace                                   *
    *                      output is slow when the trace format is *
    *                      set to Basic.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When tracing is enabled to use Memory Buffer output with Basic
    trace format, the execution time is heavily spent on retrieving
    the
    LogRecordStack for each AsyncLogRecord. This causes a
    performance
    impact on tracing, because the LogRecordStack is not needed for
    Basic trace format, it is only needed, when the trace format is
    set
    to Advanced.
    

Problem conclusion

  • The code was optimized to improve the Memory Buffer performance,
    when the trace format is Basic. The code was changed to only
    retrieve the LogRecordStack, when the trace format is set to
    Advanced.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.13 and 9.0.0.6.  Please refer to the Recommended
    Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI88370

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-05

  • Closed date

    2017-10-12

  • Last modified date

    2017-12-05

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021