Number of page sets

Using several large page sets can make the role of the WebSphere MQ administrator easier because it means that we need fewer page sets, making the mapping of queues to page sets simpler.

Using multiple, smaller page sets has a number of advantages. For example, they take less time to back up, and I/O can be carried out in parallel during backup and restart. However, consider that this adds a significant overhead to the role of the WebSphere MQ administrator, who is required to map each queue to one of a much greater number of page sets.

You are recommended to define at least five page sets, as follows:

• A page set reserved for object definitions (page set zero)

• A page set for system-related messages

• A page set for performance-critical long-lived messages

• A page set for performance-critical short-lived messages

• A page set for all other messages

Defining your buffer pools

explains the performance advantages of distributing your messages on page sets in this way.