When distributing JTPs, consider each server's capacity and the size of the entire Prinergy system. Avoid adding too many resource-intensive JTPs on one server—overloading your servers can result in poor performance and in extreme cases system failure. Before redistributing your JTPs or adding additional JTPs in your system, read these guidelines.
Important: If your Prinergy configuration and JTP distribution were set by your service representative, you should not need to redistribute your JTPs. Contact your service representative before redistributing or adding additional instances of existing JTPs
General JTP Distribution guidelines
- For larger multi-server Prinergy systems (systems with more than one secondary server), you need to offload some JTPs from the primary server to make resources available for the Oracle database software and other job management functions.
- For very large Prinergy systems (systems with more than three secondary servers), consider removing all JTPs from the primary server.
- If job replication is used, only Archiver and Purge—no other JTPs—should run on the job home server that is being replicated.
- Important Note: Prinergy Primary and Secondary servers support a maximum of 56 Job Ticket Processors of any combination, per server, in both hardware and virtual environments. This is an internal limitation of Prinergy.
JTP guidelines based on server size
The following JTP guidelines list the most resource-intensive JTPs (including disk, memory, and CPU). Although not listed here, other JTPs that are less resource-intensive may be installed on the same server.
Recommended JTP setup on a Performance server
Because the Performance server has limited resources, it is generally best to configure only one of each required type of JTP. Recommended JTP setup on a Premium server with 16 logical CPUs For a premium server that is configured with 16 logical CPUs (that is, two 8-core CPUs, such as the PE T550), you can allow up to four of the CPU-intensive output JTPs (for example, Proof256, Proof512, Print Console) on the Premium server. Generally, three refine JTPs of the same type (for example, Normalizers) are not recommended for the Premium server with 16 logical CPUs because although they are not CPU-intensive, they are disk-intensive and could saturate the local disk.
A good JTP setup for a 16-CPU server consists of:
- 2 Normalize JTPs
- 2 Optimize JTPs
- 4 Color Matcher JTPs
- 2 Trap JTPs
- 1 Import/Export JTP
- 4 Proof JTPs
- 2 Generate JTPs
- 1 or 2 additional Refine JTPs as required, while monitoring CPU, memory and disk usage.
Virtual Servers For Prinergy software running on a Kodak Virtual Operating Environment on either a VMWare or Hyper-V host, the distribution of JTPs is the same as the above, assuming the same number of vCPUs. Due to the variation of the underlying host hardware, however, some experimentation will probably be necessary.