IBM BPM, V8.0.1, All platforms > Tuning > Advanced tuning > Tuning for large objects
Select business object lazy parsing mode
For large objects, lazy parsing XML data can provide significant performance improvements over eager parsing.
The default mode for parsing business objects is eager mode, however selecting lazy parsing mode in IBM Integration Designer can provide better performance for BPEL applications. It is worth performing performance measurements to determine which mode provides the best performance for your applications. For best performance, try to avoid having modules that frequently interact with each other using different parsing modes. If mixed mode parsing is unavoidable, invocation from an eager parsing module to a lazy parsing module is more efficient than the other way around.
The following characteristics suggest that lazy parsing will provide better performance.
- Applications that use XML data streams, with business objects larger than approximately 3 KB.
- Applications that access a small portion of an XML data stream.
- WebSphere Enterprise Service Bus mediations with a mix of mediation primitives.
The following characteristics suggest that eager parsing mode will provide better performance.
- Applications that parse non-XML data streams.
- Applications that use XML messages smaller than approximately 3 KB.
- Simple WebSphere Enterprise Service Bus mediation flows that only use the following mediation primitives.
- Route on message header (message filter primitive)
- Route on message body (message filter primitive)
- XSLT primitive (if transforming on /body as the root)
- Endpoint lookup primitive without Xpath user properties
- Event emitter primitive (Common Base Event header only)
For more information about business object parsing mode, refer to the related information section.
Implications for error handing
Changing the parsing mode has implications for error handling. If the XML byte stream being parsed is ill-formed, parsing exceptions occur.
- With eager parsing, the exceptions occur as soon as the BO is parsed from the inbound XML stream.
- With lazy parsing, the parsing exceptions occur latently when the BO properties are accessed and the portion of the XML that is ill-formed is parsed.
To handle ill-formed XML for either parsing mode properly, use one of the following options:
- Deploy a mediation flow component on the application edges to validate inbound XML
- Author lazy error-detection logic at the point where BO properties are accessed.
Related information:
Business object parsing mode