The 'Default document max inline size' is an in-memory buffer that holds documents that are being processed by a LiveCycle orchestration. Its default setting is 65536 bytes (64 KB) which is too low for many orchestrations. If you proces a document larger than this value, temporary file I/O occurs to the filesystem that hosts the 'LiveCycle Temporary Folder'. If some of these transactions timeout or throw an exception, this filesystem runs the risk of running out of diskspace because of orphaned files. Periodic cleanup might be required. The folder of interest is %LC_TEMP_FOLDER%\AdobeDocumentStorage\local\.
Our tests show a 15% improvement in transaction throughput if the 'Default document max inline size' is larger than the largest document used anywhere in the orchestration. Therefore, as a performance tuning exercise, you will be better off figuring out the largest document that could possibly be used and then setting this value to a number that is higher.
You can configure this using the LiveCycle Admin UI. For 8.2.1, navigate to Settings->Core System Settings->Configurations. After making the change, the appserver instance will have to be re-started.
Values can be 1048576 (1 MB), 2097152 (2 MB) 5242880 (5 MB) or higher. However, please note that a very high value such as 300 MB will cause distress to your appserver instance's Java heap setting. In 32-bit JDK environments, such high values will increase the risk of hitting OutOfMemoryExceptions.
Depending on your use case, you will also have to increase the cache size for Forms ES as well as Output ES. In Admin UI, navigate to Services and then choose either 'LiveCycle Forms ES' or 'LiveCycle Output ES'. Change the value for Max Cache Document Size (KB) under the 'Global Cache Settings' section. Otherwise, you might get warnings such as "Ignoring cache write as Object size is greater than Max Document size in cache setting". Save the settings and then re-start the application server for these changes to take effect.
Leave a comment