The file size of forms affects performance when the server renders forms, when transferring forms over slow communication channels, or when storing or retrieving forms from near-line storage.
For forms that submit data to LiveCycle Forms ES, choose the XML Data (XML) format for the data. Other formats, such as PDF, require more bandwidth and processing time. See About submitting data using a button.
Enable form caching to increase the performance of the rendering of a form. When a form is cached, the data is merged into a pregenerated presentation. Forms whose layout adjusts to accommodate data can always be cached. Forms that have a fixed layout can also be cached, but some restrictions apply. For information about the restrictions, see Form caching. For LiveCycle Forms ES to cache forms that have a fixed layout, you must select the form caching option in LiveCycle Designer ES for each form you create.
These features cause LiveCycle Forms ES to render interactive forms. In general, non-interactive forms have a smaller file size than interactive forms and can be rendered more quickly.
If the form is intended for printing, interactive features provide no added benefit. For example, LiveCycle Designer ES can generate validation scripts for particular objects for forms that are bound to XML schemas. For interactive forms, these validation scripts ensure that data entered by the user complies with the schema specification. For example, a validation script may check that a value provided for a numeric object is an integer between 4 and 9. Non-interactive forms do not accept user input and, therefore, the validation scripts are not used. Turning off the generation of these scripts improves performance by eliminating the processing to execute them. See To set field generation options.
When rendering multiple instances of a single form, such as bills for different customers, gather the data for all the instances in a single data file and render the individual forms from this file. This approach is more efficient than processing forms individually. However, when batching different forms, group forms before rendering them. Fo
r example, if Invoices and Packing Lists are run at the same time, group and run all the Invoices, followed by all Packing Lists.
See also 

General design considerations for performance