Re: Multi CPU box for MQSI
In the NT/2000 task mgr you can right click on a process and select "Set affinity", this allows you to specify which cpu(s) a process should run on. I assume there would be a programatic method of achieving the same result. I have no idea how MQ/MQSI would react to such treatment. Matt Gurney "Potkay, Peter M (PLC, IT)" <[EMAIL PROTECTED]> THEHARTFORD.COM Sent by: MQSeries List <[EMAIL PROTECTED]> 25/11/2002 01:26 Please respond to MQSeries List To: [EMAIL PROTECTED] cc: Subject: Multi CPU box for MQSI If you had your MQSI flows running on a server that had multiple CPUs, is there away to assign Execution groups X, Y and Z to CPU #1, Execution group A to CPU #2 and the remainder of the execution groups to CPU #3? If there was a fourth CPU, would there be a way to say that all the regular QM processes ( MCAs, etc.) should use just this CPU? And the RAM would be equally shared by all regardless, correct? Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Multi CPU box for MQSI
As far as I know you cant set processor affinity under NT however you can set priorities for processes and tasks. You may want to try setting you MQ processes with a higher priority than MQSI(WMQI). After all it is WMQ that is servicing WMQI and as such you want it receiving priority. Regards Tim A "Potkay, Peter M (PLC, IT)" To: [EMAIL PROTECTED] Subject: Re: Multi CPU box for MQSI Sent by: MQSeries List 26/11/2002 01:26 Please respond to MQSeries List When MQSI is doing its thing and is real busy with heavy volume going thru an ESQL heavy compute node, the MCAs on the box get left with no resources. As a result we see XMIT queues to this box temporarily back up as the sending MCAs can't talk to the receivers, because the receivers have no available CPU. On a 2 CPU box, I would like to say, CPU#1 is only for MQSI, and #2 is for the QM and its MCAs. But maybe if there were 2 or 4 CPUs all going at the same time, the issue would not crop up anyway. Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 -Original Message- From: Bruce Olsen [mailto:[EMAIL PROTECTED]] Sent: Monday, November 25, 2002 8:58 AM To: [EMAIL PROTECTED] Subject: Re: Multi CPU box for MQSI Maybe I don't see your point, but doesn't that negate the benefits of Symmetrical Multi-Processing? Don't do for the operating system what the operating system will do for you. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Potkay, Peter M (PLC, IT) Sent: Sunday, November 24, 2002 20.26 To: [EMAIL PROTECTED] Subject: Multi CPU box for MQSI If you had your MQSI flows running on a server that had multiple CPUs, is there away to assign Execution groups X, Y and Z to CPU #1, Execution group A to CPU #2 and the remainder of the execution groups to CPU #3? If there was a fourth CPU, would there be a way to say that all the regular QM processes ( MCAs, etc.) should use just this CPU? And the RAM would be equally shared by all regardless, correct? Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Multi CPU box for MQSI
Because of the sporadic volume of messages, and the fact there are applications that need their messages ASAP, we have the BATCHINT set to zero. we need the message to go over the wire right away. I don't know if running the MCA on the MQSI queue manager as a FASTPATH app would help or not, or what the cons are to that (Paul Clarke?) But I am thinking that if you have multiple CPUs and tons of RAM, you probably don't need to worry about which CPU is doing what, because all together they can do the job, where as one couldn't. Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 -Original Message- From: David Sieberg [mailto:[EMAIL PROTECTED]] Sent: Monday, November 25, 2002 10:49 AM To: [EMAIL PROTECTED] Subject: Re: Multi CPU box for MQSI Peter, I think we are experiencing this problem also with the sending MCA on our NT qmgr/broker machines. I thought I had the same problem with the receiving MCA, although it turned out to be security related. For instance we have messages that are sent from an OS/390 qmgr to our NT qmgr/broker with put authority of CTX, and hundreds of individual users. When we restarted the NT box, or did a refresh security we would see messages buildup on the OS/390 qmgr SYSTEM.CLUSTER.TRANSMIT.QUEUE. Once the NT qmgr cached most of the userids the backlog cleared up. Because of our particular setup, we are seeing long delays when the OAM request the SID from NT for each userid. For your situation, Would running the channels and listeners as a trusted or FASTPATH application help? Can you tune the BATCHINT or BATCHSZ to make your channels more efficient? Dave "Potkay, Peter M (PLC, IT)" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Sent by: MQSeries List Subject: Re: Multi CPU box for MQSI <[EMAIL PROTECTED]> Monday November 25, 2002 09:26 AM Please respond to MQSeries List When MQSI is doing its thing and is real busy with heavy volume going thru an ESQL heavy compute node, the MCAs on the box get left with no resources. As a result we see XMIT queues to this box temporarily back up as the sending MCAs can't talk to the receivers, because the receivers have no available CPU. On a 2 CPU box, I would like to say, CPU#1 is only for MQSI, and #2 is for the QM and its MCAs. But maybe if there were 2 or 4 CPUs all going at the same time, the issue would not crop up anyway. Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 -Original Message- From: Bruce Olsen [mailto:[EMAIL PROTECTED]] Sent: Monday, November 25, 2002 8:58 AM To: [EMAIL PROTECTED] Subject: Re: Multi CPU box for MQSI Maybe I don't see your point, but doesn't that negate the benefits of Symmetrical Multi-Processing? Don't do for the operating system what the operating system will do for you. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Potkay, Peter M (PLC, IT) Sent: Sunday, November 24, 2002 20.26 To: [EMAIL PROTECTED] Subject: Multi CPU box for MQSI If you had your MQSI flows running on a server that had multiple CPUs, is there away to assign Execution groups X, Y and Z to CPU #1, Execution group A to CPU #2 and the remainder of the execution groups to CPU #3? If there was a fourth CPU, would there be a way to say that all the regular QM processes ( MCAs, etc.) should use just this CPU? And the RAM would be equally shared by all regardless, correct? Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for ma
Re: Multi CPU box for MQSI
Peter, I think we are experiencing this problem also with the sending MCA on our NT qmgr/broker machines. I thought I had the same problem with the receiving MCA, although it turned out to be security related. For instance we have messages that are sent from an OS/390 qmgr to our NT qmgr/broker with put authority of CTX, and hundreds of individual users. When we restarted the NT box, or did a refresh security we would see messages buildup on the OS/390 qmgr SYSTEM.CLUSTER.TRANSMIT.QUEUE. Once the NT qmgr cached most of the userids the backlog cleared up. Because of our particular setup, we are seeing long delays when the OAM request the SID from NT for each userid. For your situation, Would running the channels and listeners as a trusted or FASTPATH application help? Can you tune the BATCHINT or BATCHSZ to make your channels more efficient? Dave "Potkay, Peter M (PLC, IT)" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Sent by: MQSeries List Subject: Re: Multi CPU box for MQSI <[EMAIL PROTECTED]> Monday November 25, 2002 09:26 AM Please respond to MQSeries List When MQSI is doing its thing and is real busy with heavy volume going thru an ESQL heavy compute node, the MCAs on the box get left with no resources. As a result we see XMIT queues to this box temporarily back up as the sending MCAs can't talk to the receivers, because the receivers have no available CPU. On a 2 CPU box, I would like to say, CPU#1 is only for MQSI, and #2 is for the QM and its MCAs. But maybe if there were 2 or 4 CPUs all going at the same time, the issue would not crop up anyway. Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 -Original Message- From: Bruce Olsen [mailto:[EMAIL PROTECTED]] Sent: Monday, November 25, 2002 8:58 AM To: [EMAIL PROTECTED] Subject: Re: Multi CPU box for MQSI Maybe I don't see your point, but doesn't that negate the benefits of Symmetrical Multi-Processing? Don't do for the operating system what the operating system will do for you. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Potkay, Peter M (PLC, IT) Sent: Sunday, November 24, 2002 20.26 To: [EMAIL PROTECTED] Subject: Multi CPU box for MQSI If you had your MQSI flows running on a server that had multiple CPUs, is there away to assign Execution groups X, Y and Z to CPU #1, Execution group A to CPU #2 and the remainder of the execution groups to CPU #3? If there was a fourth CPU, would there be a way to say that all the regular QM processes ( MCAs, etc.) should use just this CPU? And the RAM would be equally shared by all regardless, correct? Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Multi CPU box for MQSI
When MQSI is doing its thing and is real busy with heavy volume going thru an ESQL heavy compute node, the MCAs on the box get left with no resources. As a result we see XMIT queues to this box temporarily back up as the sending MCAs can't talk to the receivers, because the receivers have no available CPU. On a 2 CPU box, I would like to say, CPU#1 is only for MQSI, and #2 is for the QM and its MCAs. But maybe if there were 2 or 4 CPUs all going at the same time, the issue would not crop up anyway. Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 -Original Message- From: Bruce Olsen [mailto:[EMAIL PROTECTED]] Sent: Monday, November 25, 2002 8:58 AM To: [EMAIL PROTECTED] Subject: Re: Multi CPU box for MQSI Maybe I don't see your point, but doesn't that negate the benefits of Symmetrical Multi-Processing? Don't do for the operating system what the operating system will do for you. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Potkay, Peter M (PLC, IT) Sent: Sunday, November 24, 2002 20.26 To: [EMAIL PROTECTED] Subject: Multi CPU box for MQSI If you had your MQSI flows running on a server that had multiple CPUs, is there away to assign Execution groups X, Y and Z to CPU #1, Execution group A to CPU #2 and the remainder of the execution groups to CPU #3? If there was a fourth CPU, would there be a way to say that all the regular QM processes ( MCAs, etc.) should use just this CPU? And the RAM would be equally shared by all regardless, correct? Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Multi CPU box for MQSI
Maybe I don't see your point, but doesn't that negate the benefits of Symmetrical Multi-Processing? Don't do for the operating system what the operating system will do for you. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Potkay, Peter M (PLC, IT) Sent: Sunday, November 24, 2002 20.26 To: [EMAIL PROTECTED] Subject: Multi CPU box for MQSI If you had your MQSI flows running on a server that had multiple CPUs, is there away to assign Execution groups X, Y and Z to CPU #1, Execution group A to CPU #2 and the remainder of the execution groups to CPU #3? If there was a fourth CPU, would there be a way to say that all the regular QM processes ( MCAs, etc.) should use just this CPU? And the RAM would be equally shared by all regardless, correct? Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
