PI43836: eXtremeMemory usage is greater than expected.

APAR status

• Closed as program error.

Error description

• When using eXtremeMemory, the reported amount of XM memory in
  xscmd's showInfo command is much higher than what is reported
  by xscmd's mapSizes command.  This descrepancy is much greater
  when using a large number of maps in a grid.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Customers that use                          *
  *                  eXtremeMemory.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: There is a large discrepency between    *
  *                      what xscmd mapsizes command reports     *
  *                      and the results of the showInfo         *
  *                      command for memory usage.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During asynchronous replication and multiple master
  replication with eXtremeMemory, a ByteBuffer is cached to avoid
  memory churn.  A ByteBuffer was being used per map.
  The logic is now updated to have ByteBuffer per primary shard
  instead.
  Additionally the eXtremeMemory usage output in xscmd's showInfo
  was updated to show both allocated and current memory usage.
  Now that the output shows current usage, the user can
  determine how much of the allocated memory is currently
  occupied with grid content.
  

Problem conclusion

• An interim fix is available for this APAR upon request.
  

Temporary fix

Comments

APAR Information

• 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

  WS EXTREME SCAL

• Fixed component ID

  5724X6702

Applicable component levels

• R860 PSY

     UP