Paul, Sorry it's taken me so long to get back. Too many other issues to look at this one. I tried amqsgetc and got the famous 2080 data truncation error. I'm trying to get another copy compiled with say a 2k buffer.
This is the most discussion that I have generated on any question to the list. Thanks for everybody and their opionions. I'll re-read all of them. To perhaps expand. We're using client here because it's free. The mainframe application uses MQ alot and it's fast for them. Just slow for the client. The queue is loaded with between several hundred and several thousand messages. The C program that they are using is very close to amqsget(c) Gets are under syncpoint (by default... the server here is OS/390) I can try and trace the client application tomorrow. It will approximate amqsget. And I will try and trace that as well when I get it recompiled with a bigger buffer. Which trace on the server (os/390) would you run? I think I can look up the client trace doc and figure that one out. Our wan is fairly robust. Pings are averaging under 20 ms. Are there any published #s for this kind of thruput in the Client with OS/390 as server? Thanks Tom ----- Original Message ----- From: "Paul Clarke" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 19, 2002 5:06 AM Subject: Re: MQ Client throughput - 2 questions >I have a situation where an MQ Client is being written to take messages off a queue on an hourly basis. The QMGR is on OS/390 and a CICS application puts messages to a >queue based on user interaction. There can be as many as 7000 (approx 120 byte) messages per hour. >The problem comes in where the MQclient for NT is trying to get the messages. When I divide out the message rate I come up with 9 messages/second. This is >unacceptable to the users. >The MQ Client for Sun Solaris does a little better (12 msg/sec). >I know that there are probably server side application changes like reading in 100 messages and putting them out as a single message with all the data strung togother. >I also know that if I run 10 copies of the client application at once then I get around 81 messages/second. But the client application is saying that the message order matters. >1) Any ideas on improving this performance. Something to tune on OS/390 client connection? >2) Is there any documented performance numbers for MQ client from OS/390 server? >TIA >Tom Tom, The first task is surely to see where the time is going. Do you even know whether the bottleneck is the MQ client or the application ? What message rate do you get if you just run something like AMQSGETC ? If it's still about 9 msg/sec then it would suggest that the problem is either in MQ or your Network. If you get significantly better performance then it would suggest the problem is with the application itself. I would suggest you run an MQ trace at both the client and server end and see where the majority of your time goes. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley 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
