HPOS 3.5 - Tuning MySQL parameters for HPOS

HP Output Server 3.5 1
Technical Note
Tuning MySQL parameters for HP Output
Server
This technical note provides information about how to tune various MySQL server parameters for HP Output Server.
Platforms affected
All platforms
Problem
The external physical destination hangs when attribute modification fails at the end of job processing.
Solution
HP Output Server 3.5 is an InnoDB-oriented application. You should tune the default values of MySQL server
tunable parameters for better performance, stability, and reliability.
Tuning with or without defragmentation of databases
HP recommends tuning MySQL with defragmentation of databases because it helps to improve performance. Before
tuning MySQL, compare the value of the innodb_data_file_path ibdata1: 250M: autoextend
parameter in the my.cnf file, which indicates the currently set size of the ibdata1 file, with the actual size of the
ibdata1 file.
If the actual size of the ibdata1 file is larger than the value set in the my.cnf file, then the database is
defragmented. Proceed with “MySQL tuning with defragmentation of databases” on page 2.
If your database is not defragmented, follow the instructions in “MySQL tuning without defragmentation of
databases” on page 3.
NOTE: With MySQL tuning, if you change the value of the
-database-client-max-connections attribute to 25 on delivery servers and
the CM server, performance should improve significantly.

Summary of content (6 pages)