| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| DataFlow Engine memory usage on a SOLARIS server |
« View previous topic :: View next topic » |
| Author |
Message
|
| hewingt |
 Posted: Mon Oct 17, 2005 1:01 am Post subject: DataFlow Engine memory usage on a SOLARIS server |
 |
|
Newbie
Joined: 10 Sep 2004
Posts: 3
Location: London
|
We are upgrading our message broker from MQSI V202 to WBIMB V5 (+FP04) on SOLARIS 8 servers.
The new broker is working as expected, but we have noticed a 10-fold increase in memory usage for each DataFlow Engine/Execution Group process.
Have other users experienced this? Is this the price we have to pay for having a better and faster broker? Or have we configured (or not configured) something we're not aware of?
All the SOLARIS servers run WMQ V53+CSD05
On all the SOLARIS servers running MQSI, all Execution Groups take 25Mb to 40Mb memory usage (as displayed by the UNIX freeware utility, top, in the SIZE column).
On all the SOLARIS servers running WBIMB, all Execution Groups take 250Mb to 400Mb memory usage. The WBIMB exe groups have the same number of flows (and instances) as the MQSI exe groups.
We are running 10 exe groups, so memory usage has increased from a total of 375Mb to 3.8Gb.
We have noticed that minimum memory usage is 250Mb after we create a new execution group with a small, simple flow.
This is not causing us any problems as our new servers have the physical memory and swap space to handle this. It only came to light when one of our older servers would not allow more than 6 WBIMB execution groups. This was because all the physical memory and swap space was in use. We resolved this by increasing the swap space.
I would like to know if other users are getting the same usage as us.
Kind Regards,
Toby Hewing & Mussadiq Ahmed |
|
| Back to top |
|
 |
| fschofer |
| Posted: Mon Oct 17, 2005 12:52 pm Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
Hi,
since Version 2.1 each Execution Group has its own Java Virtual Machine (JVM) with a default initial heap size of 128 Mb.
So this counts for at least half of your 250 Mb.
You can change this setting with the following command:
| Code: |
| mqsichangeproperties brokerName -e executionGroupLabel -o ComIbmJVMManager -n jvmMinHeapSize -v newSize |
Greetings
Frank |
|
| 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
|
|
|
|
