Best practice: Configuration recommendations to reduce memory usage

The major influence on the amount of memory that is used in processing data is the combination of the messages that are being processed, and how the flow is designed. However, the configuration of the integration broker runtime also has a significant effect on the memory usage, and it cannot be ignored.

The integration flow logic and product code of an integration server all use virtual memory. The message tree, variables, and output messages are all held at locations within virtual memory as they are processed, therefore the entire process size of the broker does not need to be held in physical memory at the same time.

The following topics provide good operating practices and configuration recommendations to reduce memory usage, regardless of the size or structure of a message to ensure that the minimum amount of physical resources are required.

The best practice information in the following sections share common approaches to solving common problems based on real customer environments. They do not provide a "one size fits all" solution. They assume that you have a basic understanding of IBM® Integration Bus. As technology evolves and improved functionality is added to the product, new recommendations and advice might be added to the information in these documents.