| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Need pointer on WAS + MQ fine tunning |
« View previous topic :: View next topic » |
| Author |
Message
|
| HenriqueS |
 Posted: Fri Sep 16, 2011 1:58 pm Post subject: Need pointer on WAS + MQ fine tunning |
 |
|
Master
Joined: 22 Sep 2006
Posts: 235
|
Hello folks,
On the WAS server side, we are facing some high CPU loads while dealing with JMS. There appears to be some sort of resource contention.
On the MQ server side, things are going well...CPU ranging 10-15% at most.
In the WAS JMS configuration panels, there are many, many connection settings that may have direct performance hit (pools, timeouts, etc.).
Is there a document that discusses best practices, problems and solutions for it ? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Sep 16, 2011 4:32 pm Post subject: Re: Need pointer on WAS + MQ fine tunning |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| HenriqueS wrote: |
Hello folks,
On the WAS server side, we are facing some high CPU loads while dealing with JMS. There appears to be some sort of resource contention.
On the MQ server side, things are going well...CPU ranging 10-15% at most.
In the WAS JMS configuration panels, there are many, many connection settings that may have direct performance hit (pools, timeouts, etc.).
Is there a document that discusses best practices, problems and solutions for it ? |
There used to be a redbook talking about the number of connections needed and the pool size as well as the maxchannels setting.
Now MQ V7 changes that some with the shareconv setting on the channel.
Have fun looking into it. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| aditya.aggarwal |
| Posted: Sun Sep 18, 2011 2:49 am Post subject: |
|
|
Master
Joined: 13 Jan 2009
Posts: 252
|
|
| Back to top |
|
|
| HenriqueS |
| Posted: Mon Oct 03, 2011 4:24 pm Post subject: |
|
|
Master
Joined: 22 Sep 2006
Posts: 235
|
Thanks for the feedback.
So far we discovered a few interesting things:
1) Mostly of the tunning is made on the WAS side. MQ software/hardware configuration, even on low end setups, is rarely any cause of performance downfall. We did increase log event size and the transaction log files tough.
2) The WAS admin books from IBM have a chapter on many of the settings effects, as well some DW site articles. We did not go into much deep on it, time was short for our system to get into production.
3) Something that increased 5 X the throughput was parallelizing the GET operations. Before we thought that the WAS JMS connection pool would have similar effect, setting a reasonable thread number on the WAS panels and hoping to fasten the loop. But we decided to parallelize the GET operation itself (10 threads). Results were impressive. |
|
| 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
|
|
|
|
