| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Performace issue - web service SOAPInput node |
« View previous topic :: View next topic » |
| Author |
Message
|
| Reva |
 Posted: Thu Jan 30, 2014 11:09 am Post subject: Performace issue - web service SOAPInput node |
 |
|
Newbie
Joined: 30 Jan 2014
Posts: 1
|
Hello,
Currently we have performance issue in our flow, it handles well with 10 concurrent users with response time of 10 to 15 secs but when it reached 15 takes more than a minute,
Flow - SOAPInput node -> Compute Node (eSQL Mapping) --> CICS call -->Compute Node --> SOAPReply node
we had suggested to deploy same message flow in to two diff EGs but we shared web service URL to consumer with single port and flow is deployed in zOS and there is only one execution group in production. is there any way to rout our incoming traffic to minimize the load?
thank you |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Jan 30, 2014 11:20 am Post subject: Re: Performace issue - web service SOAPInput node |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Reva wrote: |
| is there any way to rout our incoming traffic to minimize the load? |
What load? 15 concurrent users in a zOS execution group is not "load". What exactly is this flow doing that it takes 10 seconds with 10 users?
More importantly, when you increase to 15 users what's taking the additional 50 seconds? Where's that time going?
That's the problem you need to fix.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smuktineni |
| Posted: Fri Jan 31, 2014 5:52 am Post subject: |
|
|
Apprentice
Joined: 28 Aug 2003
Posts: 33
Location: Omaha
|
Agree with Vitor. You need to collect metrics. First establish a base line of time taken for one request. Or do load test and take average time.
Other things to look at is increase the number of instances, assuming your code is thread safe. 10/15 requests at a time is not even considered a load.
_________________
-Satish |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jan 31, 2014 6:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It's very easy to use an external http server to front-end a broker. MBX will let you export the HTTP config of a broker as either an apache mod_proxy config or a WAS plugin config file.
If you shared the URL, then change it and share the new one. Anyone who says it's a big issue to change the endpoint of a service (rather than the interface) has not done something right. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
