White Papers
Abstract
The elapsed execution time for a JSR-352 Batch application can depend on a number of decisions made as part of the design of the batch job. This design can include things like how often to checkpoint and whether to use partitions (and if so, how many partitions?). This paper takes a sample application as a baseline and explores changing values for these and other aspects of the job to determine the effect on run time for the job. If you're creating a new JSR-352 Batch job or trying to improve the performance of an existing one, this paper gives you some things to consider.
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"ARM Category":[{"code":"a8m0z000000cxwwAAA","label":"Liberty->Java Batch"},{"code":"a8m50000000CdFIAA0","label":"Performance"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
06 January 2021
UID
ibm16398358