Best Practices for memory management in Cast Iron 7.X

Size: px

Start display at page:

Download "Best Practices for memory management in Cast Iron 7.X"

Earl Douglas
5 years ago
Views:

1 IBM Software Group Best Practices for memory management in Cast Iron 7.X Subhashini Yegappan ( syegapp@us.ibm.com ) Software Support Engineer Shinsou (Al) Wang ( wangsh@us.ibm.com ) Software Support Engineer 09-June-2016

2 Agenda Latest version of Cast Iron Memory Management of Cast Iron How Orchestration design affects the memory consumption Administration perspective FAQs 2

3 IBM WebSphere Cast Iron The latest and greatest CIOS version available for IBM WebSphere Cast Iron Appliance and Hypervisor is product download link Product documentation: /mapfiles/ic_home.html 3

4 Memory allocation An integration appliance sets aside a pool of memory to run orchestration jobs. Maximum allocation for each component (Meastro, WMC, and internal Database) is 4GB. Assigning 16GB in VM would allow 4GB to assigned to each component. Version before V7 can allocate upto 3GB each per component. This requires Support to log in and manually change the setting and is reset after upgrade. 4

5 Garbage collection cycles Amount of memory directly proportional to GC. Resource utilization graph spikes at regular intervals most likely there is high demand on memory and appliance is trying to manage it by running full garbage cycles. 'Full garbage collections' stop all orchestrations, so frequent full garbage collections can affect orchestration performance. 5

6 Managing High memory usage Scenarios where high memory usage likely results in frequent full garbage collection cycles include a mix of orchestration types. For example, having multiple, non-persistent, long running orchestrations with numerous variables processing large objects. These types of orchestrations would consume and tie up large amounts of memory that could not quickly be returned to the memory pool. 6

7 Processing Large Objects Break it down to smaller chunks Using Split instead of For Each For Each is likely to create copies of object while Split uses the same object with reference pointing to child element. Calling a sub orchestration from a facade 7

8 Do you need Persistence? By default, persistence is enabled for an orchestration and variable data is written to disk instead of memory. Enabling persistence has the added benefit of point-intime data recovery should a fault occur during runtime. If you disable persistence for an orchestration, data is stored in memory. Disabling persistence can improve performance, as the number of running jobs increases the likelihood of running out of memory. Turning off persistence reduces the number of orchestration jobs that the Integration Appliance can run simultaneously. The limit is set by the amount of memory available on the Integration Appliance. 8

9 Use Scheduling to Stagger Orchestration run By scheduling memory intensive jobs to start at different times or to run during off-peak hours, you relieve some of the load on memory, reduce the number of full garbage collections, and potentially improve performance. In Studio, you can use the Schedule Job activity or configure polling intervals for activities in an orchestration to stagger orchestration jobs and maximize resource utilization. You can also create a schedule in the WMC, to control when the Integration Appliance should run an orchestration job. Measure the average execution time of a given orchestration job, so you can optimize job schedules. 9

10 Number of Variables used in an orchestration The more variables you use in an orchestration, the more memory is required to store the data. This in turn could increase the number of garbage collection cycles and affect performance. Review your orchestrations to see if you can reduce the number of variables used. 10

11 Reduce the number of simultaneously running jobs Specify the maximum number of simultaneously running jobs for an orchestration. As the number of concurrently running orchestrations increases, so does the percentage of memory usage increase. If you notice memory is getting overloaded, reduce the number of jobs running simultaneously. impactful for non-persistent, long running orchestrations jobs that contain a large number of variables. 11

12 Reduce Logging levels Detailed Logging is recommended only for Debugging purposes. Setting the System Log level to "Warning" for all components that are tracked in the system log: 1)Hardware 2)Resources 3)Network 4)Security 5)Orchestration 6)Deployment Orchestration logging levels are specified for each orchestration in a project. Cast Iron recommends setting Logging Levels to "Error Values" for all orchestrations under all projects on the Integration Appliance. 12

13 Monitoring Memory Usage In the WMC Resource Utilization Graph, you can track the percentage of memory used. When the percentage of memory used exceeds approximately 75%, you will likely notice performance issues as the number of full garbage collections increase. Consistently going over 75% is an indication that actions are needed to reduce stress of the environment. 13

14 Monitoring Garbage Collection Cycle In the WMC Resource Utilization Graph, you can use the GC Activity value to track a percentage of full garbage collections. When this percentage exceeds 50%, you might notice a reduction in the throughput of your orchestrations jobs 14

15 Add additional Integration Appliances to your environment. After implementing the best practices principles, if memory usage continues to be high, it might be time to add another Integration Appliance to your environment. 15

16 Connect with us! 1. Get notified on upcoming webcasts Send an to with subject line wste subscribe to get a list of mailing lists and to subscribe 2. Tell us what you want to learn Send us suggestions for future topics or improvements about our webcasts to wsehelp@us.ibm.com 16

17 Questions and Answers 17

18 Additional WebSphere Product Resources Learn about upcoming WebSphere Support Technical Exchange webcasts, and access previously recorded presentations at: Discover the latest trends in WebSphere Technology and implementation, participate in technically-focused briefings, webcasts and podcasts at: Join the Global WebSphere Community: Access key product show-me demos and tutorials by visiting IBM Education Assistant: View a webcast replay with step-by-step instructions for using the Service Request (SR) tool for submitting problems electronically: Sign up to receive weekly technical My Notifications s: 18

Advanced Integration Services In IBM Business Process Manager

IBM Software Group Advanced Integration Services In IBM Business Process Manager Pratima Ahuja (pratima@us.ibm.com) Software Engineer 09/11/2012 WebSphere Support Technical Exchange Agenda What is an AIS