Improving the performance of the Output service

The following list specifies performance factors to consider when working with the Output service:

  • When invoking the Output service within a process, you can improve the performance by making the process a short-lived process. A long-lived process persists data in the LiveCycle database, resulting in a performance cost.

  • As of LiveCycle 8.2, you can turn off security for the Output service. By turning off security, the Output service does not authenticate a user when it performs an operation, therefore improving the performance of a given operation.

  • Changing the caching option of the LiveCycle repository to manual optimizes performance. The default setting results in lower performance because the Output service assumes that a form (or fragments) have changed since the last time it was used.

  • Forms that contain justified fields decrease performance; that is, justification degrades performance.

  • Use of non-explicit data binding in form designs for batch processing results in decreased performance. (See Processing batch data to create multiple documents.)

  • When working with batch processing and when possible, use incremental loading. (See the section on Incremental loading)

  • When designing a form, use fonts that support a particular language to improve performance.

    Note: For information about processing large XML data files that contain many records, see Maximizing throughput.

// Ethnio survey code removed