| Author |
Message
|
| pfarrel |
 Posted: Wed Aug 08, 2012 4:20 am Post subject: WMB Startup Time |
 |
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
I am running WMB version 6.1 on AIX. We plan to go to WMB V8 but have not started that project yet.
We are concerned about the time it takes for the broker to start. After entering the mqsistart command it can take about 25 minutes before it is ready to process messages. During this time the DataFlow Engines are very busy, using a lot of CPU.
I am wondering if there is anything that can be done to improve the startup time.
I have about 60 EGs with a total of 300+ flows. All flows are MQ message driven. Reducing the number of EGs or flows is probasbly not an option. |
|
| Back to top |
|
 |
| McueMart |
| Posted: Wed Aug 08, 2012 4:27 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
| Your post is not clear. Does it take 25 minutes on WMB v6.1, or with v8? If it's 6.1, have you tried with v8? There have no doubt been many improvements. |
|
| Back to top |
|
|
| pfarrel |
| Posted: Wed Aug 08, 2012 4:34 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
| Thanks for asking, let me clarify. It takes about 25 minutes to come up using V6.1. We have not yet started our upgrade to V8, it is still in the planning stage. If V8 would provide improvements in that area we would certainly welcome that. Are you aware of any changes in that area ? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 08, 2012 4:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pfarrel wrote: |
| Thanks for asking, let me clarify. It takes about 25 minutes to come up using V6.1. |
Which version of v6.1? It shouldn't take that long. Do any of the flows do anything "custom" on startup.
My experiencee of v6.1 on AIX (4 sites over 3 years) is that it takes around 5 minutes to get out of bed, have coffee & start processing. Typically that's with a smaller number of EGs but an equivalent number of flows. I do suspect that whatever's causing that anomolous start time on v6.1 may well cause it on v8 as well.
What rules out reduceing EGs as an option? I accept reducing flows means recoding, retesting and all sorts of stuff.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pfarrel |
| Posted: Wed Aug 08, 2012 5:01 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
| We are running 6.1.0.7. The flows go to an MQ Input node and wait for a message to arrive. Several of them have multiple instances. Memory constraint is a big issue which prevents us from having too many flows in an EG. All EGs are in pairs, so that one of the pair can continue to run while we are deploying to the other. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Aug 08, 2012 5:33 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
WMB V8 has significant performance enhancements, especially if running on POWER7 with AIX 7.1. In this environment, it takes our Broker instances about three to four minutes to initialize completely and start listening on the SOAP ports.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Aug 08, 2012 5:33 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Has it always taken 25 minutes? Or did this behavior change recently? Suddenly?
Is the AIX box sufficiently provisioned (RAM, cpu)?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| pfarrel |
| Posted: Wed Aug 08, 2012 6:11 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
It has been like that for a long time unfortunately.
During startup the box runs 100 percent, but usage is lower when running processing messages. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 08, 2012 6:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pfarrel wrote: |
| Memory constraint is a big issue which prevents us from having too many flows in an EG. |
Touches to my point about "custom" activity. If you have flows which building big memory structures and/or doing a huge amount of initialization outside the normal broker startup then it's unlikely anything will really help. WMBv8 does have improvements, but it's more likely to just mean it takes 20 minutes rather than 25.
You need to bite the bullet and find out where this time is going. What exactly are the EGs doing for 25 minutes? That's a lot longer than it should take to open some queues.
| pfarrel wrote: |
| During startup the box runs 100 percent, but usage is lower when running processing messages. |
How much lower? If it stabalizes at 80% CPU after 25 minutes and starts processing messages, you have resource problems.
I'd still look for "custom" code; perhaps something that initializes a monitoring or chargeback solution, something that reads & caches a lot of data or something that builds a big memory structure.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Aug 08, 2012 6:56 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
| pfarrel wrote: |
It has been like that for a long time unfortunately.
During startup the box runs 100 percent, but usage is lower when running processing messages. |
100% of what? cpu? What about I/O rate? What about paging rate? RAM?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Aug 08, 2012 9:56 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
At my last place of employment we used 6.1 on Solaris.
The broker regularly took 45 minutes to startup and read a steady state of operation. During this time the CPU was 100% and several execution groups restated due to timeouts. Most of these were ones that contained many (> 20) flows.
The CPU limitations were due to licensing were the main problem. 99% of the time in operations the CPU would not max out but during startup...
It would be nice if there was a more flexible approach here. One where the license was based upon uisage during steady state operations would be nice. Sigh
Jyust to say that your experiences are not unique.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
