Author |
Message
|
sido |
Posted: Wed Apr 19, 2006 11:19 pm Post subject: Performance Improvement |
|
|
Novice
Joined: 02 Feb 2004 Posts: 23
|
Hi,
I have a flow that does the following -
a) a set of validations on several tables
b) a series of inserts/updates based on the same.
The Environment is AIX 5.3 and WBIMB 5.0 CSD 6.
All tables are on the same Database on DB2 8.1.
If I try to deploy the flow multiple times, it starts giving me deadlock issues. As a result, I split the functionality into two flows - one that did validations and the other that did the insert/update logic.
Despite this, I find that deploying the flow multiple times is not improving the performance.
Please help! |
|
Back to top |
|
 |
JLRowe |
Posted: Wed Apr 19, 2006 11:31 pm Post subject: |
|
|
 Yatiri
Joined: 25 May 2002 Posts: 664 Location: South East London
|
The database is your bottleneck, look at using less restrictive locks to improve concurrency. I would suggest you dive into the DB2 manuals or talk to your DBA (if you have one). |
|
Back to top |
|
 |
elvis_gn |
Posted: Wed Apr 19, 2006 11:33 pm Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi sido,
Quote: |
If I try to deploy the flow multiple times |
Do u mean that u have increased the number of instances of the flow...or trying to deploy the same flow with different parameters for input...or...??
Quote: |
giving me deadlock issues |
Can you please post the error logs.
Regards. |
|
Back to top |
|
 |
sido |
Posted: Thu Apr 20, 2006 12:01 am Post subject: |
|
|
Novice
Joined: 02 Feb 2004 Posts: 23
|
Hi elvis,
I am trying to deploy the same flow several times...there are no erros on a/c of this - just that the flow is not moving any faster which typically is what happens!
sido |
|
Back to top |
|
 |
sirsi |
Posted: Thu Apr 20, 2006 2:24 pm Post subject: |
|
|
Disciple
Joined: 11 Mar 2005 Posts: 177
|
deplyoing the flow several times wont increase the performance.. this has to do with the tuning database only |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Apr 20, 2006 3:16 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You can only "deploy the flow several times" to different execution groups.
Every time you deploy a flow to the same execution group, you replace the flow on that EG.
You can increase the instances of a flow on a particular EG - this will increase the threads that are running copies of that flow on that EG.
This will also cause any database contention to increase.
As sirsi says, you should tune your database to make sure that it can handle the correct number of connections that meet your requirements for processing speed.
This requires you to know your requirements for processing speed, and to know how many db connections the Broker makes for each instance of a broker flow, and each instance of an EG and etc, and know how many of those connections will be active at the same time.
Maybe you should just ask your DBA to tune this for you. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
sido |
Posted: Thu Apr 20, 2006 10:31 pm Post subject: |
|
|
Novice
Joined: 02 Feb 2004 Posts: 23
|
Hi,
I guess I wasnt clear. My 'Validations' flow is the one that has been deployed on several execution groups and this helps as there is independant Validations running at its pace and Independant Inserts running at its pace. Test Environment is Windows + MQSI 2.1 - hence the term.
My Insert/Update flow is still running only one instance.
We tried to force a 'Commit' after every Insert/Update operation but still gives issues.
Guess its DBA time! |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Apr 21, 2006 3:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
If you're getting database contention/deadlocks, you need to work with your DBA to understand why. Then you need to go back and examine how your flows are using the database, and read the manuals on how database connections are used and managed within WMB and how transactions are created and committed. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
sirsi |
Posted: Tue Apr 25, 2006 12:13 pm Post subject: |
|
|
Disciple
Joined: 11 Mar 2005 Posts: 177
|
Production is WBIMB v5 and test is WMQI v2.1 .. interesting.
WMQI is becoming obsolete.. |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Apr 25, 2006 4:21 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
sirsi wrote: |
Production is WBIMB v5 and test is WMQI v2.1 .. interesting.
WMQI is becoming obsolete.. |
WBIMB v5 is becoming obsolete.
WMQI is obsolete. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
|