| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| High static memory utilization by EG |
« View previous topic :: View next topic » |
| Author |
Message
|
| alagarsamy |
 Posted: Sat Sep 27, 2008 3:46 am Post subject: High static memory utilization by EG |
 |
|
Newbie
Joined: 03 Sep 2008
Posts: 5
|
Hi
We have 7-10 complex message flows deployed in a single EG which has Httpinput nodes as well as mqinput nodes.
The EG has been configured to use a maximum of 512MB ram through mqsichangeproperties command with -o ComIbmJVMManager option.
The EG Dataflowengine process tooks around 700 MB even when starting the broker and there were no traffic flowing.
There were no additional threads configured on each message flows.
So what is making this EG to utilize 700 MB even when passive/broker was just started?.
Also it has been observed that when traffic flows through this EG,its utilization got increased upto 2GB and is not getting released even after the requests are serviced,Any clues here?.
The Total memory utilization in the solaris server(having 28GB RAM) is reaching 83% out of majority being utilized by 4 such EG's consuming 2GB each.
Any one to help me here...IBM PMR(61185) raised as well for this.
Regards,
Suresh |
|
| Back to top |
|
 |
| SAFraser |
| Posted: Thu Oct 02, 2008 10:18 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
Suresh,
If you learn anything of interest as the result of your PMR, I would be grateful if you would post it.
I am currently collapsing EGs on a Solaris server to reduce the WMB footprint in memory, as physical memory stays ~88% and swap memory bounces ~90-94%.
Although, in our case, we have way too many brokers on this one server....
Thanks very much. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Oct 02, 2008 3:13 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The JVM memory heap is only half the runtime. Let us not forget that there is also a C runtime in Broker!
There are options, and alas I don't recall them, to control the EGHeap rather than the JVM Heap. |
|
| Back to top |
|
|
| hopsala |
| Posted: Mon Oct 06, 2008 7:41 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
I have noticed similar behavior in one of my environments - memory increase which, at some point, stabilizes around a given memory limit (2GB in your case) even when there's no traffic. I think this is a result of the way the garbage collector works. Maybe the 512MB limit is an "active objects" limit, who knows.
If we're talking java flows, it might do some good to look into the MbMessage.clearMessage() method, even though its precise effect isn't really documented, other than that it "clears allocated resources". Hopefully it should allow for quicker garbage collector and a lower memory footprint.
As the fair SAFraser said, I am also keen to hear of your progress. Keep us posted! |
|
| 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
|
|
|
|
