Should I use this old machine to run my production queue manager?
ColinPaice 120000E7BQ Visits (1555)
We have had a couple of questions about which file system people should use for their distributed production queue manager.
One person said they found an old server which had never been used. They put a current Linux on it, and ran a queue manager which became the production queue manager.
Full marks for reuse - but it did not give the throughput they needed, so no marks for planning.
We also had a question asking if we could come up with a tool or document which could predict the throughput for a given file system and persistent message profile.
These questions are both connected. Starting from an existing file system and putting a queue manager on it is approaching the problem the wrong way.
You should approach the planning from an architectural and a business perspective. The Agile approach of "Fail Fast Fail Often" is not a good strategy for this.
From an architectural perspective
From a business perspective
To find if your environment can achieve the required throughput and meet the response time criteria, you need to run a workload similar to your peak workload to see.
One word of warning - do this during peak activity - not late at night when the system is not being used - as you want the disk load, and the network load you will get when running it in production.
I discussed this with Tony Sharkey MQ on z/OS Performance and he summarised it as