| Author |
Message
|
| ANILK |
 Posted: Mon Dec 29, 2014 1:15 am Post subject: Performance Issue - Data inserting and updating to ORACLE |
 |
|
Acolyte
Joined: 01 May 2014
Posts: 61
|
Hi Friends,
I am using WMB 8.2, we are facing a production issue ,
we have independent flows for data insertion in to Oracle Database.
some times those Queues getting piled up quickly. we suspect it could be because of slow DB interaction.
we got a report from DBA that , WMB is not terminating the connections with DB even after inserting the record and this could be the reason for the slow performance.
1) is there any solution to increase the performance . ?
2)do we need to do any code tuning to fix this issue ?
3) is this a code bug ? , do we need to add any function in this code as part of best practice ?
Please help me to get some info to fix this issue .
Thanks
ANILK |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Dec 29, 2014 5:24 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
My understanding is that the reason for not terminating the connection to the DB is in order to reuse it. (Performance booster).
Now what you should be looking at is your commit load. A commit load of say 100 is much faster than a commit load of 1 when doing multiple repeatable DB insertions...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ANILK |
| Posted: Mon Dec 29, 2014 8:30 am Post subject: |
|
|
Acolyte
Joined: 01 May 2014
Posts: 61
|
Hi fjb_saper,
Thank you for your reply , how to control the "commit load" where i need to verify this .
Anil |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Dec 29, 2014 1:13 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| ANILK wrote: |
Hi fjb_saper,
Thank you for your reply , how to control the "commit load" where i need to verify this .
Anil |
Bar file properties...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| McueMart |
| Posted: Mon Dec 29, 2014 4:34 pm Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
Just to clarify, "Commit count" is the property you want to google/search the infocenter for.
The first thing you always want to do when someone points the finger at Broker and blames it for 'performance issues', is first clarify where the issue actually lies. Can you DBAs observe if queries are taking a long time? If this is the case, it's almost certainly a DB issue, and not Broker's fault (Bad indexes, inefficient queries etc etc).
I highly doubt this is related to Broker's connection pooling implementation (which will keep connections open until they have been idle for a period of time). |
|
| Back to top |
|
|
| ANILK |
| Posted: Mon Dec 29, 2014 6:52 pm Post subject: |
|
|
Acolyte
Joined: 01 May 2014
Posts: 61
|
Thank you for sharing your suggestions, i will update my comments, after discussing with the DBA
Anil |
|
| Back to top |
|
|
| ghoshly |
| Posted: Tue Dec 30, 2014 7:35 am Post subject: Try to get a pattern |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
I have faced similar challenge from outsiders 
You just need to prove them the right way of doing things....Try to get a pattern for the performance with single messages and with some load of messages... with simple records and with big / CLOB records etc. That should help to identify the pin point of performance issue.
Make sure there are not other database locks on the same table where you are trying to insert.
Verify total number of connection pool allowed for that specific DB user which you are using to insert.
Verify the connectivity between WMB and DB server; whether they are in same data center or in different places. |
|
| Back to top |
|
|
|
|
