JMS queue file placement: performance
You can review the information about performance of the JMS queue throughput.
The IBM® MQ logs and files and the WebLogic JMS file and paging stores can be implemented on an internal disk. Message queues on a single internal disk should be able to provide from 150K to 200K messages per hour. Obviously, many factors can affect the message throughput including the size of the message content, the burstiness of the traffic, and so forth).
For high transaction systems, for example, a nightly upload of global inventory visibility messages or the import of point-of-sales orders, you should consider placing the IBM MQ logs and files and the Oracle WebLogic JMS file and paging stores on a SAN RAID-10 LUN, possibly with a large NVRAM cache. The striping component in the RAID-10 spreads the message I/Os over multiple disks. The NVRAM cache could reduce the number of physical disk I/Os.
In extremely high transaction volume scenarios, you may have to consider implementing multiple WebLogic JMS servers or MQ queue managers. This is applicable to solutions where the message order is not important.
Availability
For failover and high availability, you should consider placing the IBM MQ logs and files and the WebLogic JMS file stores for persistent queues on an external SAN. In the event of a node failure, a standby node could attach to the SAN to access the files. In addition, you could replicate the content of the SAN to prevent message loss in the event of a data center disaster.
Parameters
See the following topics for specific recommendations: