| Author |
Message
|
| meena05 |
 Posted: Wed Aug 31, 2016 12:14 am Post subject: IIB MQ Instances |
 |
|
Apprentice
Joined: 26 Feb 2016
Posts: 39
|
Hi,
I have single instance of IIB V9 flow with MQ Input ->Compute -> SOAP Request -> Compute -> MQ Reply
We have 25k - 30K mq requests coming into the queue with expiry of 15 seconds.
I have increased node instances to 4 and was able to process 5K + records on first run. Expired would be resent again by the application.
However, requirement is to process 12K + records in the first run. I have increased instances to 8 on MQ Input Node but I still see only 5000+ records getting processed.
Can anyone advise on how can I increase throughput to grab 12k+ records within 15 sec. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Aug 31, 2016 12:53 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
could the bottleneck be the WebService?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| vishBroker |
| Posted: Wed Aug 31, 2016 8:30 am Post subject: |
|
|
Centurion
Joined: 08 Dec 2010
Posts: 135
|
| smdavies99 wrote: |
| could the bottleneck be the WebService? |
I agree!!
Try to gather latency details. Most importanty for SOAP request.
Alternatively - you can skip SOAP request and see - how much time IIB is taking => This will help you identify latency caused by 2 compute nodes.
You can use some dummy message to put in replyTo queue.
And what is meant by 1st run.
You are saying 12k transactions ,,but in what time?
What is the required TPS?
If you do ot see any latency in IIB processing -> Then you can start looking into how IIB is reading the messages from queue.
# of connections to the QM, Status of channel etc. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Aug 31, 2016 11:16 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
Unless you are accessing external resources (like a database) in the compute node then you have probably saturated the web service. Try running more instances of the web service.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| meena05 |
| Posted: Thu Sep 01, 2016 11:10 am Post subject: |
|
|
Apprentice
Joined: 26 Feb 2016
Posts: 39
|
| Thank you all for your reply. Analyzed the service call. Thats the one consuming most of the time causing delays. Increasing expiry on request messages solved the problem! |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Sep 01, 2016 9:22 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY
|
| meena05 wrote: |
| Thank you all for your reply. Analyzed the service call. Thats the one consuming most of the time causing delays. Increasing expiry on request messages solved the problem! |
No it did not. It just shifted it a little.
You need to look at the service and determine why it can't keep up... and may be run more instances of it... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
