PQ58984: SIGNIFICANT PERFORMANCE DEGRADATION IS NOTED WHEN SMF EVENT AND ACTIVITY RECORDING IS ENABLED FOR WEBSPHERE

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Problem
Without any activity or interval SMF records being written by th
server or container, the application ran at approximately 400
transactions/second with a .04 second response time as observed
the (Mercury LoadRunner) client.
SMF Interval Records:
With SMF server & container interval records being written at an
interval of five minutes, the same appl. ran at approximately
130 transactions/second with a .16 second response time.
Local fix
Do not enable SMF recording for the WAS container.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: Turning SMF recording on causes         *
*                      performance to deteriorate              *
*                      significantly.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Tuning SMF recording on causes performance to deteriorate
significantly. Improvement modifications in SMF Recording are
needed.
Problem conclusion
Performance during SMF recording has been improved by doing the
following:

1. SMF recording support has been modified such that unguarded
   calls to Trace methods are no longer done. Testing is now
   done to determine if Tracing is enabled before calling
   the method.

2. The many calls to tputv have been removed.

3. The implementation of ws390uuid.class created a large number
   of Java String Objects. ws390wsuuid has been restructured to
   make one return String on the toString method. In addition,
   the create of the hashcode is not done until it is called
   for.

APAR PQ58984 is associated with SERVICE LEVEL W401060 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ58984
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-03-12
Closed date 2002-05-09
Last modified date 2002-06-05

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOOAACI BBOOABM BBOOACCI BBOOACQE BBOOACQW BBOOAET
BBOOAGEV BBOOAIM BBOOAIMR BBOOAIMS BBOOAMR BBOOAPBC
BBOOAPCI BBOOARCI BBOOARMR BBOOARMW BBOOAS1 BBOOAS2
BBOOAS3 BBOODGAI BBOODGCA BBOODQCA BBOODQEB BBOODRAI
BBOODSAB BBOODSM BBOOEVAS BBOOHA BBOOSMFP BBOOSMFR
BBOOSMFW BBOOSS BBOUBINF BBOZ0812 BBOZ0813  

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ66083    UP02/05/17 P F205

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ58984
IBM Group: Software Group
Modified date: Jun 5, 2002