MQSeries.net :: View topic - Aggregation Node Performance Issues

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Aggregation Node Performance Issues

Aggregation Node Performance Issues

« View previous topic :: View next topic »

Author

Message

mbtech

Posted: Tue Feb 19, 2013 6:13 am Post subject: Aggregation Node Performance Issues

Apprentice

Joined: 18 Jul 2012
Posts: 36

I developed a flow where iam using a SOAP input and aggregation nodes
for multi user and multi instances its consuming time of 17 sec now my job is to reduce the time taken and improve the performance of it.

At SOAP input node
HTTP Transport property
Does Maximum wait time increasing will improve performance?
Does using HTTPS improves?
Enabling support for WSDL improves?

At AGGREGATE contro;
Does time out increase improves performance?

Any inputs for improving performance of aggregation flow using soap inputs for multi user and multi instances are welcome

Thanks in advance

mqjeff

Posted: Tue Feb 19, 2013 6:21 am Post subject: Re: Aggregation Node Performance Issues

Grand Master

Joined: 25 Jun 2008
Posts: 17447

mbtech wrote:

HTTP Transport property

No.

mbtech wrote:

Does Maximum wait time increasing will improve performance?

No.

mbtech wrote:

Does using HTTPS improves?

No.

mbtech wrote:

Enabling support for WSDL improves?

No.

mbtech wrote:

At AGGREGATE contro;
Does time out increase improves performance?

No.

mbtech wrote:

Any inputs for improving performance of aggregation flow using soap inputs for multi user and multi instances are welcome

The only thing that can be done is to DETERMINE where the performance issue is OCCURING.

This means you have to measure it. Measuring the roundtrip and then flipping switches at random does not mean you have measured anything.

Take a user trace of the flow. Accept that this will slow down the over all performance, and yet magically give you timing for each individual piece of the flow and so you can see which piece is actually taking the most time.

Then fix the identified slow areas.

And notice that you can't say they are fixed until you can show that previously they took X time and now they take X-K time.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Aggregation Node Performance Issues

Jump to:

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

Protected by Anti-Spam ACP