Forums | Admin

Discussion Forums: open-discussion

Start New Thread Start New Thread
Message: 64272
BY: Praveen Devarao (praveend)
DATE: 2009-01-27 14:33
SUBJECT: Ruby ibm_db Adapter and Excessive SQL calls

 

Hi,

Below I am pasting the mail extract so that others going through the forum will get the context of the conversation

__________________________________________________
Our database team noticed that some of the SQL statements are getting executed repeatedly causing CPU spikes on DB server.

We did came to a conclusion (assumption) that IBM Ruby adapter is making those calls to retrieve the meta data information from the database.

If our assumption is correct , Is it possible for the IBM Ruby adapter to cache this information and reuse it instead of going against the database.

Any optimization in this regard will improve our database performance .

This is what our DBA team is reporting.

The following two queries are executing thousands of times. They are coming from the application ID so something is driving these statements. You will need to track them down and determine if any of this information being queried can be cached. Both queries are using AP907011.

VALUES ( LENGTH ( :H00003 ) ) This query executed 226304 times in a 15 minute time period.
INTO :H00016 :H00017

VALUES ( SUBSTR ( :H00003 , :H00014 , :H00015 ) ) This query executed 113151 times in the same 15 minute window.
INTO :H00009 :H00017
___________________________________________________



Thread View

Thread Author Date
Ruby ibm_db Adapter and Excessive SQL callsPraveen Devarao2009-01-27 14:33
      RE: Ruby ibm_db Adapter and Excessive SQL calPraveen Devarao2009-01-27 14:36
            RE: Ruby ibm_db Adapter and Excessive SQL calvenkata yerrapothu2009-02-07 21:22
                  RE: Ruby ibm_db Adapter and Excessive SQL calPraveen Devarao2009-02-09 02:01
                        RE: Ruby ibm_db Adapter and Excessive SQL calGeorge Keenan2009-04-06 22:42
                  RE: Ruby ibm_db Adapter and Excessive SQL calGeorge Keenan2009-04-07 13:50

Post a followup to this message