Here are a few easy ways to improve performance when using the Output service with forms.
Use explicit data binding on the formThe Output service merges the form data with the form design before rendering the form. If the form uses a data connection to retrieve the form data, you should explicitly bind the form fields and subforms to data items explicitly. Explicit data binding causes the Output service to immediately match data nodes with form fields. If you use Normal binding, the Output service follows a set of rules to determine data node and form field associations. Normal binding requires more processing time than explicit binding. To learn how to bind data explicitly, see To bind a node to an existing field in Adobe LiveCycle Designer ES Help.Note: When a form field is not bound to an item in the data source, set the Default Binding property of the field to None so that the Output service doesn’t attempt to find an associated data node. See To remove a binding.Embed fonts only when necessaryEmbedding fonts in PDF forms increases the file size, and so, increases the time required to process the form. You do not need to embed fonts if the fonts reside on the target printer that the Output service sends the form to. When possible, use fonts that reside on the target printer in your form designs so that you don’t have to embed them.If you need to embed fonts, avoid using OpenType fonts when the target printer uses PCL as the print stream. PCL printers rasterize OpenType fonts, resulting in large print files and longer print times.Use Incremental LoadingMerging very large amounts of data with a form design can cause the LiveCycle ES server to run out of memory. If you are using multi-record data sets, you can configure the Output service to load and merge one record of data at a time. This incremental (lazy) loading of data avoids running out of memory because only one record is stored in memory at one time.Both the generatePDFOutput and generatePrintedOutput operations can perform incremental loading. On the process diagram, you configure the Batch properties (in the PDF Output Options property group) of either operation to define the data items that comprise a record of data. You can use the Record Name property or the Record Level property to define the record. (See generatePDFOutput and generatePrintedOutput in LiveCycle Workbench ES Help. On both of those pages, click the Input heading to see the information.)To enable incremental loading, you also need to configure the form to enable incremental loading. Form designs that include the <xfa:datasets> element prevent the Output service from performing incremental loading. You need to remove the datasets element and all of its child elements from the form design. Use the XML Source view in Designer to remove the datasets element. For more information about the datasets element, and for more form design tips for the Output service, see Designing Forms for LiveCycle Output ES.