The document summarizes findings from a project testing batch processing performance using J2EE. It discusses considerations for batch frameworks, infrastructure, caching, logging, design challenges, and whether to use batch processing. It also outlines the design of the batch process used, including leveraging raw JDBC, Oracle caching, and tools for performance monitoring.

1. Batch Processing With J2EE Chris Adkin 28 th December 2008 Last Updated 13 th May 2009

4. Design Considerations

50. Batch Architecture Deployment Diagram

55. Batch Design Sequence Diagram batch Client batch Client J2EE Container J2EE Container Database Database 1: Start the Batch process 3: Get no.of threads and no.of jobs per thread parameters 5: returns 6: Get the list of SPRs/Jobs to be processed 8: returns a list of SPRs / Job Ids 9: Create No.of threads and pass the 'job list' as parameter 10: Each thread makes a call to a Bean method by sending the ' job list' as parameter 12: On completion, each thread ends here 11: Loop through each SPR/ Job Id within the 'job list' to process them 4: Retrieve the parameters 7: Retrive the SPRs/Job Ids 2: Create a Batch record with Start time 13: Update the Batch record with Status, end time

57. Design Critique

71. Testing Environment

85. Identifying Bottlenecks

90. The ‘Carrot’ Model

91. Software Configuration Base Line

97. Tuning

119. Tuning Results Summary

124. Critique Of Tools Used

130. Conclusions

145. Is The Database The Bottleneck ? 94.13 % Non-Parse CPU: 24.76 Parse CPU to Parse Elapsd %: 99.91 Latch Hit %: 91.14 Execute to Parse %: 99.99 Soft Parse %: 99.99 Library Hit %: 100.00 In-memory Sort %: 99.33 Buffer Hit %: 100.00 Redo NoWait %: 99.99 Buffer Nowait %: