| Author |
Message
|
| yaakovd |
 Posted: Thu Jun 05, 2003 4:16 pm Post subject: Workflow optimization |
 |
|
Partisan
Joined: 20 Jan 2003
Posts: 319
Location: Israel
|
WorkFlow 3.3 on AIX (6 CPU), DB2 7.2, MQ 5.2
ExecutionServer – 6 instances.
- Cleanup server settings
- Check interval PT5M
- Start mode Immediate
- Cleanup time P1W
- Cleanup delay time PT1H
- Scheduling server settings
- Check interval PT2M
- Start mode Immediate
- Notification check interval PT5S
- Suspension check interval PT1H
- Create notification items threshold 10
- Delete notification items threshold 100
From time to time Workflow accumulates till 1500 messages in EXEXMLINPUTQ.
We are looking for optimization…
What is optimal number of execution servers?
What impact of current Cleanup server and Scheduling server settings?
Thanks,
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
| Back to top |
|
 |
| Ratan |
| Posted: Thu Jun 05, 2003 10:35 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
how many process Instances are created per day and how many activities per processes? I am not sure about how Cleanup server and Scheduling server settings are related to the number of messages on EXEXMLINPUTQ, but the Scheduling server setting of 2M and 5S are very resource intensive.
_________________
-Ratan |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Jun 06, 2003 4:50 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Yakov:
I seem to recall hearing that 2 * the number of processesors is the place to start for ES. I may have read this on the IBM newsgroup.
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| manoj |
| Posted: Fri Jun 06, 2003 2:18 pm Post subject: |
|
|
Master
Joined: 30 Jan 2002
Posts: 237
Location: Virgina
|
Since u 've 6 CPUs theoretically u can go for 6*2+2 = 14 execution server instances. But considering other factors (say clean upserver, scheduling server etc) u should be keeping the number around 10.
The other thing i noticed is that the check interval u keep is very small. This will eat up some resource.
One more thing u may want to do is to set the value for "RTRecyclethreshold" (i don't remember the exact keyword !!!). Since too many execution servers running u can keep it large (say 5000).
What this does is the execution server instance die after every 5000 transactions and starts a new instance there by realeasing some resource.
_________________
-manoj |
|
| Back to top |
|
|
| Ratan |
| Posted: Fri Jun 06, 2003 2:33 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
| Quote: |
Since u 've 6 CPUs theoretically u can go for 6*2+2 = 14 execution server instances. But considering other factors (say clean upserver, scheduling server etc) u should be keeping the number around 10.
|
Number of CPUs * 2 is a suggestion from IBM for number of exec servers, but keeping in mind that you have DB2 also on the machine, I have no clue how many ESs you can run.
_________________
-Ratan |
|
| Back to top |
|
|
| yaakovd |
| Posted: Mon Jun 09, 2003 7:04 pm Post subject: |
|
|
Partisan
Joined: 20 Jan 2003
Posts: 319
Location: Israel
|
Thanks to all 
seems like there is no deadlocks in DB2, but WF accumulates the messages in EXEXMLINPUTQ; We can use 8-10 Execition servers and change check intervals...
We have only MQSeries, DB2 and WF on this server.
Thanks again.
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
| Back to top |
|
|
|
|
