How to Improve Adobe Livecycle Performance
Running Adobe LiveCycle with its default factory settings may not meet your specific needs. In addition, a number of outside influences affect how well Adobe LiveCycle performs. Every business is different, so initial and ongoing performance tuning is necessary to optimize resource management and ultimately to help improve the performance of Adobe LiveCycle.
Other People Are Reading
Instructions
-
-
1
Approach LiveCycle performance tuning from a perspective that includes both the application and the environment in which it runs. Important areas of concern include form design, solution components, the choice, location and size of the database server, available memory on the database and application server, processor considerations, infrastructure architecture, available network bandwidth, scalability, configuration settings, security systems and desktop infrastructure.
-
2
Create a performance tuning team that includes a database administrator and network administrator. Because MySQL database and network performance tuning require advanced knowledge and a skill set you may not possess, both may be necessary to optimize the environment in which LiveCycle runs.
-
-
3
Use the internal tools LiveCycle provides for monitoring and improving performance. The LiveCycle Health Monitor — accessible from the main menu bar on the Administrators Console — has both a System and a WorkManager view. The System view allows you to monitor physical and heap memory, CPU use and historical charts. The WorkManager view provides work queue statistics on jobs, workflows and LiveCycle events.
-
4
Monitor the size of the heap — an area reserved for dynamic memory allocation — using JConsole, an external tool that comes with the Java Platform, and make adjustments as necessary from the Administration Console to ensure its size is about 20 percent larger than what LiveCycle is currently using, but no larger than its maximum 2 gigabyte size. Optimizing the size of the heap helps reduce memory requirements in the Java Virtual Machine.
-
5
Adjust the max inline size from its default of 64 kilobytes to one that is just larger than the file size you use most often. This setting, which determines whether in-memory document data storage occurs in the heap or in Global Document Storage, should be low to avoid placing large documents in the heap and triggering more frequent garbage collections. If you set the max inline size to 40K, documents that take up less than 40KB of storage space will go in the heap and documents 40KB and larger will go to the GDS. Use the "Settings" tab on the LiveCycle Administration Console to navigate first to "Core System" and then to "Core Configurations" to make this adjustment.
-
6
Analyze process flow to see how much time each step in an individual process takes to run. The Process Design tab on the LiveCycle WorkBench IDE -- integrated development environment -- allows you to record a process as it runs, play it back and then view performance results from a log file. Viewing each step as a separate action identifies those requiring tuning via code modification.
-
1
References
Resources
- Photo Credit Stockbyte/Stockbyte/Getty Images
