PI79686: Slow response when using batchpersistence in Liberty

Fixes are available

APAR status

Closed as program error.

Error description

A JSR-352 Compute Grid batch application is configured to
run
on WebSphere Liberty Profile 16.0.0.4 with the jobRepository
configured on DB2. During the application run it was
observed
that when the Chunk type batch application handles a large
amount of data, the processing speed becomes very slow.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty- Batch                       *
****************************************************************
* PROBLEM DESCRIPTION: Performance issues when running a batch *
*                      job with a chunk step with a large      *
*                      number of records                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Prior to this fix, a database read was performed after each item
was read and processed within a chunk step, to see if the job
was stopping (if a 'stop' had been issued by an administrator).
For a step with a large number of records, the aggregate time
spent checking for a stop could be substantial.

Problem conclusion

For steps which are executing co-located to the "top-level"
(this basically means everything but a "remote partition"
executing on a different server), the check to see if the job is
stopping is performed against an in-memory flag, rather than
against the database, improving aggregate elapsed time for a job
processing a large number of records.

The fix for this APAR is currently targeted for inclusion in fix
pack 17.0.0.2.  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
PI79686
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-04-10
Closed date
2017-05-18
Last modified date
2017-05-18

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
LIBERTY PROFILE
Fixed component ID
5724J0814

Applicable component levels

RCD0 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI79686: Slow response when using batchpersistence in Liberty

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

RCD0 PSY

Document Information

Share your feedback

Need support?