Bad performance with PreparedStatement

Hi,
I have a query that returns about 10.000 results on which I have to iterate.
The query is something like that :
SELECT col1,col2 FROM myTable INNER JOIN myTable2 using(id) WHERE time > TO_DATE('15/06/2009 16:28:00','DD/MM/YY HH24:MI:SS') AND time < TO_DATE('16/06/2009 2:35:00','DD/MM/YY HH24:MI:SS');
This query is ultra fast using a basic Statement, It iterate over all line of the cursor in less than 100ms.
The date parts of the query are generated using string concatenation.
Since it's a bad practice I have decided to use a PreparedStatement and so to change the query like that :
SELECT col1,col2 FROM myTable INNER JOIN myTable2 using(id) WHERE time > ? AND time < ?;
I bind the dates and I get exactly the same result, except the performance... Now it doesn't take 100ms... It take about 120000ms (2min)!!!?
The execution of the query is not the problem, the problem comes from the ResulSet.next() method that is much longer than before.
I precise that the exactly same values are used, the result is exactly the same.
I have tried different value for the fetch size but no big differences.
An idea?

Sorry I have answer too fast. I have still performance issue when using the query :
SELECT col1,col2
FROM myTable
INNER JOIN myTable2 using(id)
WHERE time > TO_TIMESTAMP(?,'DD/MM/YY HH24:MI:SS.FF')
AND time < TO_TIMESTAMP(?,'DD/MM/YY HH24:MI:SS.FF')
PreparedStatement stmt = connection.prepareStatement(
SimpleDateFormat sf = new SimpleDateFormat("dd/MM/yy HH:mm:ss.SSS");
stmt.setString(1, sf.format(fromDate));
stmt.setString(2, sf.format(toDate));while the following query perfectly work :
SimpleDateFormat sf = new SimpleDateFormat("dd/MM/yy HH:mm:ss.SSS");
SELECT col1,col2
FROM myTable
INNER JOIN myTable2 using(id)
WHERE time > TO_TIMESTAMP('" + sf.format(fromDate) + "','DD/MM/YY HH24:MI:SS.FF')
AND time < TO_TIMESTAMP(('" + sf.format(toDate) + "','DD/MM/YY HH24:MI:SS.FF')Really bored of oracle products...

Similar Messages

  • Bad performance with brandnew system

    hello,
    i set up a completely new win7-64bit based on a fresh osx (snow-leopard update) on a fresh harddisk....and i have very bad 3d performance with only 3 (!!) programs installed. i am working with autodesk 3ds max and autocad and both run very slow. my last system was win7-64bit, too, but running MUCH faster.
    it must be a driver problem, but i dont know how to change the nvidia driver.
    edit:
    after having changed driver from directx 9 to open-gl performance is very fast.
    please help.
    alex
    Message was edited by: mbp_3d

    Hi Bruno
        In the following Re: Generic Sync: Object can not be deserilized / Multiple synchronization call you had mentioned that you are using MI 2.5 SP16 Client.  For your information MI doesnt support Windows Mobile 5 OS on SP16 but only from SP18 does it support this OS.  Have you tried upgrading the client to any of the SPs i had mentioned in the above thread and then checked the performance?
    Best Regards
    Sivakumar

  • Bad performance with Payables Open Interface Import

    hello all
    have a performance problem with the standard program Payables Open Interface Import, as this process is taking a long time to run.
    could recommend some patch for this issue or a solution.
    our application is 11.5.10.2 and Database 10g
    now create a SR but to date we have not been sending the first plan of action
    best regards

    There are many reasons this is a performance problem - search in MOS for "APXIIMPT performance" or "payables open interface import performance"
    Your best bet is to work this thru an SR.
    Have you traced the concurrent to determine where the bottleneck is ? Are statistics current ?
    HTH
    Srini

  • Bad performance with many xmlqueries in select and big resultset

    I'm running into big performance problems with the following query (edited the query a bit to remove sensitive information):
    SELECT id "id",created "created",
      xmlcast(xmlquery('declare default element namespace "http://www.example.com/myproject/schema/namespace2";declare namespace c="http://www.example.com/myproject/schema/common";/element1/element2/name' passing xml returning content) as varchar2(182))"element2Name",
      xmlcast(xmlquery('declare default element namespace "http://www.example.com/myproject/schema/namespace2";declare namespace c="http://www.example.com/myproject/schema/common";/element1/element3/name' passing xml returning content) as varchar2(182))"element3Name",
      xmlcast(xmlquery('declare default element namespace "http://www.example.com/myproject/schema/namespace2";declare namespace c="http://www.example.com/myproject/schema/common";/element1/ror/gcor' passing xml returning content) as varchar2(5))"gcor",
      xmlcast(xmlquery('declare default element namespace "http://www.example.com/myproject/schema/namespace2";declare namespace c="http://www.example.com/myproject/schema/common";/element1/c:element1Header/c:status/c:cStatus' passing xml returning content) as integer)"cStatus",
      xmlcast(xmlquery('declare default element namespace "http://www.example.com/myproject/schema/namespace2";declare namespace c="http://www.example.com/myproject/schema/common";/element1/c:element1Header/c:status/c:lrrm' passing xml returning content) as integer)"lrrm",
      xmlcast(xmlquery('declare default element namespace "http://www.example.com/myproject/schema/namespace2";declare namespace c="http://www.example.com/myproject/schema/common";/element1/c:element1Header/c:status/c:sent' passing xml returning content) as integer)"sent",
      xmlcast(xmlquery('declare default element namespace "http://www.example.com/myproject/schema/namespace2";declare namespace c="http://www.example.com/myproject/schema/common";/element1/c:element1Header/c:status/c:success' passing xml returning content) as integer)"success",
      xmlcast(xmlquery('declare default element namespace "http://www.example.com/myproject/schema/namespace2";declare namespace c="http://www.example.com/myproject/schema/common";/element1/c:element1Header/c:status/c:processStep' passing xml returning content) as integer)"processStep",
      xmlcast(xmlquery('declare default element namespace "http://www.example.com/myproject/schema/namespace2";declare namespace c="http://www.example.com/myproject/schema/common";/element1/header/status/aseod' passing xml returning content) as number(1))"aseod",
      xmlcast(xmlquery('declare default element namespace "http://www.example.com/myproject/schema/namespace2";declare namespace c="http://www.example.com/myproject/schema/common";/element1/submission/deferred' passing xml returning content) as number(1))"deferred",
      xmlcast(xmlquery('declare default element namespace "http://www.example.com/myproject/schema/namespace2";declare namespace c="http://www.example.com/myproject/schema/common";/element1/header/status/eventReportReceived' passing xml returning content) as number(1))"eventReports",
      xmlcast(xmlquery('declare default element namespace "http://www.example.com/myproject/schema/namespace2";declare namespace c="http://www.example.com/myproject/schema/common";/element1/c:element1Header/c:status/c:isOpen' passing xml returning content) as number(1))"isOpen",
      xmlcast(xmlquery('declare default element namespace "http://www.example.com/myproject/schema/namespace2";declare namespace c="http://www.example.com/myproject/schema/common";/element1/c:element1Header/c:hasNotes' passing xml returning content) as number(1))"hasNotes"
    FROM tablename,xmltable(xmlnamespaces(default 'http://www.example.com/myproject/schema/namespace2','http://www.example.com/myproject/schema/common' as "c"),'/element1' passing xml columns
    created timestamp path 'c:element1Header/c:creationTime/text()',
    organization_id integer path 'c:element1Header/c:organization/c:organizationId/text()',
    is_sender number(1) path 'c:element1Header/c:isSender/text()')
    WHERE organization_id = 5 AND is_sender = 1 AND created >= sysdate-20 AND created <= sysdate+1;This query is fast as long as the results is small (<1000), but when the resultset grows bigger, the performance seems to decrease exponentially. The cause of this slowdown seems to be in the xmlqueries; commenting out the xmlqueries makes the query very fast again (in the order of a few seconds), even with a 15000+ resultset, while including the xmlqueries makes the query take many minutes.
    Workaround I tried: using a rownum < 1000 works fairly well, but only if I don't use order by (which is required). order by forces the resultset to be full built regardless of the rownum limit. (this was done with a subquery orderby and a rownum on the superquery)
    Other workaround i tried: Having the subquery only return the xml column, and doing the xmlqueries in the superquery. I couldn't get this to work, something about no longer having a key-preserved table.
    Background info about the database: Oracle 11.2.0.3.0, binary xmltype column, with a xmlindex unstructured component on all paths in this query, and a structured component with secondary indexes on the paths used in the WHERE (created, organization_id and is_sender). Database has about 140k records total.
    My question is, if anyone knows if this xmlquery bottleneck can be remedied somehow?
    Addition: graph i made indicating the performance at different resultset sizes. Horizontal axis is size of resultset, vertical axis is time spent in seconds: http://i.imgur.com/F2tyg.png

    Just count(*), nothing else in the select:
    COUNT(*)              
    15432                 
    Plan hash value: 1584286506
    | Id  | Operation                      | Name                  | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT               |                       |     1 |    39 |    31   (0)| 00:00:01 |
    |   1 |  SORT AGGREGATE                |                       |     1 |    39 |            |          |
    |*  2 |   FILTER                       |                       |       |       |            |          |
    |   3 |    NESTED LOOPS                |                       |    15 |   585 |    31   (0)| 00:00:01 |
    |   4 |     TABLE ACCESS BY INDEX ROWID| TABLENAME_SC          |    15 |   405 |    16   (0)| 00:00:01 |
    |*  5 |      INDEX RANGE SCAN          | TABLENAME_SC_SUB_IX   |    15 |       |     3   (0)| 00:00:01 |
    |   6 |     TABLE ACCESS BY USER ROWID | TABLENAME             |     1 |    12 |     1   (0)| 00:00:01 |
    Predicate Information (identified by operation id):
       2 - filter(SYSDATE@!-500<=SYSDATE@!-50)
       5 - access("SYS_SXI_0"."ORGANIZATION_ID"=6 AND "SYS_SXI_0"."IS_SENDER"=1 AND
                  "SYS_SXI_0"."CREATION_TIME">=SYSDATE@!-500 AND "SYS_SXI_0"."CREATION_TIME"<=SYSDATE@!-50)Original query with ORDER BY on 2 structured component columns, 1 descending and 1 ascending (NOTE: While the explain plan says the time is 00:00:01, the query takes 763 seconds to complete)
    | Id  | Operation                      | Name                           | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT               |                                |    15 | 23880 |    32   (4)| 00:00:01 |
    |   1 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |*  2 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    17 |   697 |     5   (0)| 00:00:01 |
    |*  3 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |   4 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |*  5 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    16 |   656 |     5   (0)| 00:00:01 |
    |*  6 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    16 |       |     3   (0)| 00:00:01 |
    |   7 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |*  8 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    15 |   615 |     4   (0)| 00:00:01 |
    |*  9 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    15 |       |     3   (0)| 00:00:01 |
    |  10 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 11 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    17 |   697 |     5   (0)| 00:00:01 |
    |* 12 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |  13 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 14 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    17 |   697 |     5   (0)| 00:00:01 |
    |* 15 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |  16 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 17 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    17 |   697 |     5   (0)| 00:00:01 |
    |* 18 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |  19 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 20 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    17 |   697 |     5   (0)| 00:00:01 |
    |* 21 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |  22 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 23 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    17 |   697 |     5   (0)| 00:00:01 |
    |* 24 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |  25 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 26 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |     1 |    41 |     4   (0)| 00:00:01 |
    |* 27 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |     1 |       |     3   (0)| 00:00:01 |
    |  28 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 29 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |     8 |   328 |     4   (0)| 00:00:01 |
    |* 30 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |     8 |       |     3   (0)| 00:00:01 |
    |  31 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 32 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |     1 |    41 |     4   (0)| 00:00:01 |
    |* 33 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |     1 |       |     3   (0)| 00:00:01 |
    |  34 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 35 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    17 |   697 |     5   (0)| 00:00:01 |
    |* 36 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |  37 |  SORT ORDER BY                 |                                |    15 | 23880 |    32   (4)| 00:00:01 |
    |* 38 |   FILTER                       |                                |       |       |            |          |
    |  39 |    NESTED LOOPS                |                                |    15 | 23880 |    31   (0)| 00:00:01 |
    |  40 |     TABLE ACCESS BY INDEX ROWID| TABLENAME_SC                   |    15 |  1350 |    16   (0)| 00:00:01 |
    |* 41 |      INDEX RANGE SCAN          | TABLENAME_SC_SUB_IX            |    15 |       |     3   (0)| 00:00:01 |
    |  42 |     TABLE ACCESS BY USER ROWID | TABLENAME                      |     1 |  1502 |     1   (0)| 00:00:01 |
    Predicate Information (identified by operation id):
       2 - filter(SYS_XMLI_LOC_ISNODE("SYS_P1"."LOCATOR")=1)
       3 - access("SYS_P1"."RID"=:B1 AND "SYS_P1"."PATHID"=HEXTORAW('509D') )
       5 - filter(SYS_XMLI_LOC_ISNODE("SYS_P3"."LOCATOR")=1)
       6 - access("SYS_P3"."RID"=:B1 AND "SYS_P3"."PATHID"=HEXTORAW('4FDE') )
       8 - filter(SYS_XMLI_LOC_ISNODE("SYS_P5"."LOCATOR")=1)
       9 - access("SYS_P5"."RID"=:B1 AND "SYS_P5"."PATHID"=HEXTORAW('7129') )
      11 - filter(SYS_XMLI_LOC_ISNODE("SYS_P7"."LOCATOR")=1)
      12 - access("SYS_P7"."RID"=:B1 AND "SYS_P7"."PATHID"=HEXTORAW('73C0') )
      14 - filter(SYS_XMLI_LOC_ISNODE("SYS_P9"."LOCATOR")=1)
      15 - access("SYS_P9"."RID"=:B1 AND "SYS_P9"."PATHID"=HEXTORAW('3092') )
      17 - filter(SYS_XMLI_LOC_ISNODE("SYS_P11"."LOCATOR")=1)
      18 - access("SYS_P11"."RID"=:B1 AND "SYS_P11"."PATHID"=HEXTORAW('30AA') )
      20 - filter(SYS_XMLI_LOC_ISNODE("SYS_P13"."LOCATOR")=1)
      21 - access("SYS_P13"."RID"=:B1 AND "SYS_P13"."PATHID"=HEXTORAW('3415') )
      23 - filter(SYS_XMLI_LOC_ISNODE("SYS_P15"."LOCATOR")=1)
      24 - access("SYS_P15"."RID"=:B1 AND "SYS_P15"."PATHID"=HEXTORAW('4972') )
      26 - filter(SYS_XMLI_LOC_ISNODE("SYS_P17"."LOCATOR")=1)
      27 - access("SYS_P17"."RID"=:B1 AND "SYS_P17"."PATHID"=HEXTORAW('745F') )
      29 - filter(SYS_XMLI_LOC_ISNODE("SYS_P19"."LOCATOR")=1)
      30 - access("SYS_P19"."RID"=:B1 AND "SYS_P19"."PATHID"=HEXTORAW('6BA9') )
      32 - filter(SYS_XMLI_LOC_ISNODE("SYS_P21"."LOCATOR")=1)
      33 - access("SYS_P21"."RID"=:B1 AND "SYS_P21"."PATHID"=HEXTORAW('62DB') )
      35 - filter(SYS_XMLI_LOC_ISNODE("SYS_P23"."LOCATOR")=1)
      36 - access("SYS_P23"."RID"=:B1 AND "SYS_P23"."PATHID"=HEXTORAW('1FD9') )
      38 - filter(SYSDATE@!-500<=SYSDATE@!-50)
      41 - access("SYS_SXI_0"."ORGANIZATION_ID"=6 AND "SYS_SXI_0"."IS_SENDER"=1 AND
                  "SYS_SXI_0"."CREATION_TIME">=SYSDATE@!-500 AND "SYS_SXI_0"."CREATION_TIME"<=SYSDATE@!-50)
    Note
       - Unoptimized XML construct detected (enable XMLOptimizationCheck for more information)The same query with ORDER BY only on CREATED DESC (takes 15 seconds to complete):
    | Id  | Operation                      | Name                           | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT               |                                |    15 | 23880 |    31   (0)| 00:00:01 |
    |   1 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |*  2 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    17 |   697 |     5   (0)| 00:00:01 |
    |*  3 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |   4 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |*  5 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    16 |   656 |     5   (0)| 00:00:01 |
    |*  6 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    16 |       |     3   (0)| 00:00:01 |
    |   7 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |*  8 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    15 |   615 |     4   (0)| 00:00:01 |
    |*  9 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    15 |       |     3   (0)| 00:00:01 |
    |  10 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 11 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    17 |   697 |     5   (0)| 00:00:01 |
    |* 12 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |  13 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 14 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    17 |   697 |     5   (0)| 00:00:01 |
    |* 15 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |  16 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 17 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    17 |   697 |     5   (0)| 00:00:01 |
    |* 18 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |  19 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 20 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    17 |   697 |     5   (0)| 00:00:01 |
    |* 21 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |  22 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 23 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    17 |   697 |     5   (0)| 00:00:01 |
    |* 24 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |  25 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 26 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |     1 |    41 |     4   (0)| 00:00:01 |
    |* 27 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |     1 |       |     3   (0)| 00:00:01 |
    |  28 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 29 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |     8 |   328 |     4   (0)| 00:00:01 |
    |* 30 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |     8 |       |     3   (0)| 00:00:01 |
    |  31 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 32 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |     1 |    41 |     4   (0)| 00:00:01 |
    |* 33 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |     1 |       |     3   (0)| 00:00:01 |
    |  34 |  SORT GROUP BY                 |                                |     1 |    41 |            |          |
    |* 35 |   TABLE ACCESS BY INDEX ROWID  | SYS63339_TABL_XML_I_PATH_TABLE |    17 |   697 |     5   (0)| 00:00:01 |
    |* 36 |    INDEX RANGE SCAN            | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |* 37 |  FILTER                        |                                |       |       |            |          |
    |  38 |   NESTED LOOPS                 |                                |    15 | 23880 |    31   (0)| 00:00:01 |
    |  39 |    TABLE ACCESS BY INDEX ROWID | TABLENAME_SC                   |    15 |  1350 |    16   (0)| 00:00:01 |
    |* 40 |     INDEX RANGE SCAN DESCENDING| TABLENAME_SC_SUB_IX            |    15 |       |     3   (0)| 00:00:01 |
    |  41 |    TABLE ACCESS BY USER ROWID  | TABLENAME                      |     1 |  1502 |     1   (0)| 00:00:01 |
    Predicate Information (identified by operation id):
       2 - filter(SYS_XMLI_LOC_ISNODE("SYS_P1"."LOCATOR")=1)
       3 - access("SYS_P1"."RID"=:B1 AND "SYS_P1"."PATHID"=HEXTORAW('509D') )
       5 - filter(SYS_XMLI_LOC_ISNODE("SYS_P3"."LOCATOR")=1)
       6 - access("SYS_P3"."RID"=:B1 AND "SYS_P3"."PATHID"=HEXTORAW('4FDE') )
       8 - filter(SYS_XMLI_LOC_ISNODE("SYS_P5"."LOCATOR")=1)
       9 - access("SYS_P5"."RID"=:B1 AND "SYS_P5"."PATHID"=HEXTORAW('7129') )
      11 - filter(SYS_XMLI_LOC_ISNODE("SYS_P7"."LOCATOR")=1)
      12 - access("SYS_P7"."RID"=:B1 AND "SYS_P7"."PATHID"=HEXTORAW('73C0') )
      14 - filter(SYS_XMLI_LOC_ISNODE("SYS_P9"."LOCATOR")=1)
      15 - access("SYS_P9"."RID"=:B1 AND "SYS_P9"."PATHID"=HEXTORAW('3092') )
      17 - filter(SYS_XMLI_LOC_ISNODE("SYS_P11"."LOCATOR")=1)
      18 - access("SYS_P11"."RID"=:B1 AND "SYS_P11"."PATHID"=HEXTORAW('30AA') )
      20 - filter(SYS_XMLI_LOC_ISNODE("SYS_P13"."LOCATOR")=1)
      21 - access("SYS_P13"."RID"=:B1 AND "SYS_P13"."PATHID"=HEXTORAW('3415') )
      23 - filter(SYS_XMLI_LOC_ISNODE("SYS_P15"."LOCATOR")=1)
      24 - access("SYS_P15"."RID"=:B1 AND "SYS_P15"."PATHID"=HEXTORAW('4972') )
      26 - filter(SYS_XMLI_LOC_ISNODE("SYS_P17"."LOCATOR")=1)
      27 - access("SYS_P17"."RID"=:B1 AND "SYS_P17"."PATHID"=HEXTORAW('745F') )
      29 - filter(SYS_XMLI_LOC_ISNODE("SYS_P19"."LOCATOR")=1)
      30 - access("SYS_P19"."RID"=:B1 AND "SYS_P19"."PATHID"=HEXTORAW('6BA9') )
      32 - filter(SYS_XMLI_LOC_ISNODE("SYS_P21"."LOCATOR")=1)
      33 - access("SYS_P21"."RID"=:B1 AND "SYS_P21"."PATHID"=HEXTORAW('62DB') )
      35 - filter(SYS_XMLI_LOC_ISNODE("SYS_P23"."LOCATOR")=1)
      36 - access("SYS_P23"."RID"=:B1 AND "SYS_P23"."PATHID"=HEXTORAW('1FD9') )
      37 - filter(SYSDATE@!-500<=SYSDATE@!-50)
      40 - access("SYS_SXI_0"."ORGANIZATION_ID"=6 AND "SYS_SXI_0"."IS_SENDER"=1 AND
                  "SYS_SXI_0"."CREATION_TIME">=SYSDATE@!-500 AND "SYS_SXI_0"."CREATION_TIME"<=SYSDATE@!-50)
    Note
       - Unoptimized XML construct detected (enable XMLOptimizationCheck for more information)Removing all XmlQueries from the SELECT and adding 1 of them to the XmlTable in the FROM (full table scan, takes 25 seconds to complete):
    | Id  | Operation                    | Name                           | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT             |                                |  1522 |  2232K| 15515   (3)| 00:03:07 |
    |   1 |  TABLE ACCESS BY INDEX ROWID | TABLENAME_SC                   |     1 |    21 |     2   (0)| 00:00:01 |
    |*  2 |   INDEX RANGE SCAN           | SYS63339_63348_RID_IDX         |     1 |       |     1   (0)| 00:00:01 |
    |   3 |  TABLE ACCESS BY INDEX ROWID | TABLENAME_SC                   |     1 |    32 |     2   (0)| 00:00:01 |
    |*  4 |   INDEX RANGE SCAN           | SYS63339_63348_RID_IDX         |     1 |       |     1   (0)| 00:00:01 |
    |   5 |  TABLE ACCESS BY INDEX ROWID | TABLENAME_SC                   |     1 |    23 |     2   (0)| 00:00:01 |
    |*  6 |   INDEX RANGE SCAN           | SYS63339_63348_RID_IDX         |     1 |       |     1   (0)| 00:00:01 |
    |   7 |  TABLE ACCESS BY INDEX ROWID | TABLENAME_SC                   |     1 |    27 |     2   (0)| 00:00:01 |
    |*  8 |   INDEX RANGE SCAN           | SYS63339_63348_RID_IDX         |     1 |       |     1   (0)| 00:00:01 |
    |   9 |  TABLE ACCESS BY INDEX ROWID | TABLENAME_SC                   |     1 |    18 |     2   (0)| 00:00:01 |
    |* 10 |   INDEX RANGE SCAN           | SYS63339_63348_RID_IDX         |     1 |       |     1   (0)| 00:00:01 |
    |  11 |  TABLE ACCESS BY INDEX ROWID | TABLENAME_SC                   |     1 |    13 |     2   (0)| 00:00:01 |
    |* 12 |   INDEX RANGE SCAN           | SYS63339_63348_RID_IDX         |     1 |       |     1   (0)| 00:00:01 |
    |* 13 |  TABLE ACCESS BY INDEX ROWID | SYS63339_TABL_XML_I_PATH_TABLE |     1 |    37 |     4   (0)| 00:00:01 |
    |* 14 |   INDEX RANGE SCAN           | SYS63339_TABL_XML_I_PIKEY_IX   |    17 |       |     3   (0)| 00:00:01 |
    |* 15 |  FILTER                      |                                |       |       |            |          |
    |* 16 |   TABLE ACCESS FULL          | TABLENAME                      |  1522 |  2232K|  9423   (4)| 00:01:54 |
    |  17 |   TABLE ACCESS BY INDEX ROWID| TABLENAME_SC                   |     1 |    13 |     2   (0)| 00:00:01 |
    |* 18 |    INDEX RANGE SCAN          | SYS63339_63348_RID_IDX         |     1 |       |     1   (0)| 00:00:01 |
    |  19 |   TABLE ACCESS BY INDEX ROWID| TABLENAME_SC                   |     1 |    13 |     2   (0)| 00:00:01 |
    |* 20 |    INDEX RANGE SCAN          | SYS63339_63348_RID_IDX         |     1 |       |     1   (0)| 00:00:01 |
    |  21 |   TABLE ACCESS BY INDEX ROWID| TABLENAME_SC                   |     1 |    21 |     2   (0)| 00:00:01 |
    |* 22 |    INDEX RANGE SCAN          | SYS63339_63348_RID_IDX         |     1 |       |     1   (0)| 00:00:01 |
    |  23 |   TABLE ACCESS BY INDEX ROWID| TABLENAME_SC                   |     1 |    21 |     2   (0)| 00:00:01 |
    |* 24 |    INDEX RANGE SCAN          | SYS63339_63348_RID_IDX         |     1 |       |     1   (0)| 00:00:01 |
    Predicate Information (identified by operation id):
       2 - access("SYS_SXI_7"."RID"=:B1)
       4 - access("SYS_SXI_6"."RID"=:B1)
       6 - access("SYS_SXI_5"."RID"=:B1)
       8 - access("SYS_SXI_4"."RID"=:B1)
      10 - access("SYS_SXI_3"."RID"=:B1)
      12 - access("SYS_SXI_2"."RID"=:B1)
      13 - filter(SYS_XMLI_LOC_ISTEXT("SYS_P0"."LOCATOR","SYS_P0"."PATHID")=1)
      14 - access("SYS_P0"."RID"=:B1 AND "SYS_P0"."PATHID"=HEXTORAW('509D') )
      15 - filter(CAST(TO_NUMBER(SYS_XQ_UPKXML2SQL(SYS_XQEXVAL( (SELECT
                  SYS_XQ_PKSQL2XML("SYS_SXI_11"."ORGANIZATION_ID",2,4,2) FROM "USERN"."TABLENAME_SC" "SYS_SXI_11" WHERE
                  "SYS_SXI_11"."RID"=:B1),0,0,54525952,0),50,1,2)) AS integer )=6 AND
                  CAST(TO_NUMBER(SYS_XQ_UPKXML2SQL(SYS_XQEXVAL( (SELECT SYS_XQ_PKSQL2XML("SYS_SXI_10"."IS_SENDER",2,4,2)
                  FROM "USERN"."TABLENAME_SC" "SYS_SXI_10" WHERE "SYS_SXI_10"."RID"=:B2),0,0,54525952,0),50,1,2)) AS
                  number(1) )=1 AND CAST(TO_TIMESTAMP(SYS_XQ_UPKXML2SQL(SYS_XQEXVAL( (SELECT
                  SYS_XQ_PKSQL2XML("SYS_SXI_9"."CREATION_TIME",180,8,2) FROM "USERN"."TABLENAME_SC" "SYS_SXI_9" WHERE
                  "SYS_SXI_9"."RID"=:B3),0,0,20971520,0),50,1,2),'SYYYY-MM-DD"T"HH24:MI:SSXFF') AS timestamp
                  )>=SYSDATE@!-300 AND CAST(TO_TIMESTAMP(SYS_XQ_UPKXML2SQL(SYS_XQEXVAL( (SELECT
                  SYS_XQ_PKSQL2XML("SYS_SXI_8"."CREATION_TIME",180,8,2) FROM "USERN"."TABLENAME_SC" "SYS_SXI_8" WHERE
                  "SYS_SXI_8"."RID"=:B4),0,0,20971520,0),50,1,2),'SYYYY-MM-DD"T"HH24:MI:SSXFF') AS timestamp
                  )<=SYSDATE@!-200)
      16 - filter(EXISTSNODE(SYS_MAKEXML(0,"SYS_ALIAS_11"."SYS_NC00003$"),'/oraxq_defpfx:element1','
                  xmlns:oraxq_defpfx="http://www.example.com/myproject/schema/namespace2"')=1)
      18 - access("SYS_SXI_11"."RID"=:B1)
      20 - access("SYS_SXI_10"."RID"=:B1)
      22 - access("SYS_SXI_9"."RID"=:B1)
      24 - access("SYS_SXI_8"."RID"=:B1)Index creation script:
    CREATE INDEX tabl_xml_ix
      ON tablename(xml)
      INDEXTYPE IS XDB.XMLIndex
      PARAMETERS('
        PATHS (INCLUDE (/element1/common:header/common:kind
    /element1/common:element1Header/common:referenceNumber
    /element1/common:element1Header/common:reference
    /element1/common:element1Header/common:organization/common:organizationId
    /element1/common:element1Header/common:status/common:cStatus
    /element1/common:element1Header/common:status/common:isOpen
    /element1/common:element1Header/common:status/common:processStep
    /element1/common:element1Header/common:status/common:lrrm
    /element1/common:element1Header/common:status/common:sent
    /element1/common:element1Header/common:status/common:success
    /element1/common:element1Header/common:creationTime)
                       NAMESPACE MAPPING (xmlns="http://www.example.com/myproject/schema/namespace2"
                            xmlns:common="http://www.example.com/myproject/schema/common"))');
    ALTER INDEX tabl_xml_ix
    PARAMETERS ('PATHS (INCLUDE ADD (/element1/e/referenceCode
    /element1/e/header/sNumber
    /element1/element2/name
    /element1/element3/name
    /element1/element4/id
    /element1/submission/deferred
    /element1/common:element1Header/common:organization/common:pNumber
    /element1/e/iNumber
    /element1/header/status/aseod
    /element1/common:element1Header/common:isSender
    /element1/ror/gcor
    /element1/header/status/eventReportReceived
    /element1/pod/eNumber)
                       NAMESPACE MAPPING (xmlns="http://www.example.com/myproject/schema/namespace2"
                            xmlns:common="http://www.example.com/myproject/schema/common"))');
    BEGIN
      DBMS_XMLINDEX.registerParameter(
        'tablename_add_sc','ADD_GROUP GROUP tablename_group
    XMLTABLE tablename_sc
    XMLNAMESPACES(
    DEFAULT ''http://www.example.com/myproject/schema/namespace2'',
    ''http://www.example.com/myproject/schema/common'' AS "common"
    ''/element1''
    COLUMNS
    is_sender NUMBER(1) path ''common:element1Header/common:isSender/text()'',
    creation_time TIMESTAMP PATH ''common:element1Header/common:creationTime/text()'',
    rn VARCHAR2(22 CHAR) PATH ''common:element1Header/common:referenceNumber/text()'',
    rc VARCHAR2(21) PATH ''e/referenceCode/text()'',
    reference VARCHAR2(35 CHAR) PATH ''common:element1Header/common:reference/text()'',
    i_nr VARCHAR2(35 CHAR) PATH ''e/iNumber/text()'',
    p_nr VARCHAR2(32) PATH ''common:element1Header/common:organization/common:pNumber/text()'',
    pod_e_nr VARCHAR2(13) PATH ''pod/eNumber/text()'',
    d_id VARCHAR2(16) PATH ''element4/id/text()'',
    organization_id INTEGER PATH ''common:element1Header/common:organization/common:organizationId/text()'',
    sequence_number INTEGER PATH ''e/eHeader/sequenceNumber/text()''
    END;
    ALTER INDEX tabl_xml_ix PARAMETERS('PARAM tablename_add_sc');
    create index tablename_sc_rn_ix on tablename_sc(rn);
    create index tablename_sc_time_ix on tablename_sc(creation_time);
    create index tablename_sc_sub_ix on tablename_sc (organization_id, is_sender, creation_time);Edited by: Michiel Weggen on Apr 11, 2012 2:02 AM Reason: Forgot secondary indexes.
    Edited by: Michiel Weggen on Apr 11, 2012 5:51 AM: changed path of d_id to element4/id in the structured component

  • Bad performance with non-cumulative key figures

    Hi All,
    I have a cube with 8 non cumulative key figures based on fiscper.
    I am not sure how the performance for reporting with non-cumulatives can be improved.
    Thanks
    Karen

    Performance of non cumulative cubes is dependant on the distance between the marker (date of the last compression) and the execution date.
    For actual stock, the more you compress the better it is.
    Regards,
    Fred

  • XML Publisher has bad performance with 10 concurrent users.

    PeopleTools version:Tools: 8.48.09
    OS/RDBMS Version*( required for Tools Forums): Oracle 10.2.0.4
    Application type and version:
    Description of the Problem/Question:
    Customer currently testing a process which exposes XML publisher functionality via self service. The process calls an app engine which
    generates an XML file, processed by XML Publisher, and then displayed in the browser window.
    They have found that any more than ten or so users in our test environment (two app servers, one web server per app server) seems to slow
    the process to a halt, even causing some requests to go unprocessed. The bottleneck seems to be at the web server (WebLogic) as the
    database and app server performance metrics are very good, however PeopleSoft Ping suggests that the web server is having trouble.
    production environment has 8 app servers, one web server per app server. Are there any configuration changes we can make to improve
    the serving of PDFs from XML publisher output? Add more web servers per app server? WebLogic java VM heap settings?
    WebLogic Server 8.1 SP5
    Tuxedo: Version 8.1, 64-bit, Patch Level 192
    Any other thoughts on performance degrade with XML Publisher with more than 10 users.
    Are there any configuration changes we can make to improve the serving of PDFs from XML publisher output? Add more web servers per app server?
    Thanks

    There are currently two known operations that are seriously slower in update 10:
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6635462
    and
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6652116
    (taken from the release notes).
    You can disable the hardware pipeline to basically go back to the old situation as it was in update 7 if it is giving your problems. I wouldn't know why simple fill actions would be bogging it down though, it smells like something is done wrong in your app.

  • Bad Performance with Oracle Lite 4.0.1

    I have a table in Oracle Lite with 17000 records and 110 fields. A SELECT on this table needs 1 minute to finish. The same table and query only needs 1 second on Oracle 8i Server. MSDE also needs 1 second. All the relevant fields are indexed. Are there any parameters in Oracle Lite that we can tweak? Is there something else I'm forgetting?

    Hi Shivek,
    An excellent solution for this is provided in the metalink Note:455905.1.
    Let me know if you have more questions.
    Thanks
    Vishnu

  • Bad performances with both catalyst and free driver

    Hello,
    With the  catalyst driver 15.20 and Xorg 1.16 my graphic card(hd 7870) is not used at her maximum for example in kerbal space program i have beetween 45% and 88% Gpu load but only in place like oceans normaly it don't exceed 75%, i have the same issue in war thunder,star conflict,robocraft but with unigine benchmark's (valley and heaven) it is good. I dont think it is normal . The cpu isn't overloaded it is a i5 3570.
    What can i do?
    Last edited by remy18 (2015-06-02 17:57:59)

    Understood ewaller
    I tried with another distribution (caculate linux) and i have the same issue so this is normal but i don't know why...
    Last edited by remy18 (2015-06-11 15:52:50)

  • Very Bad performance with high stress on Tempdb

    Hello ,
    below is the execution plan for a query rapidly increase the Tempdb and has very slow performance,
    appreciate your suggestion to enhance this query (any data is available upon request) 

    >Covering indexes will make a huge difference.
    You can't simply "create-covering-index" yourself out from every performance jam.
    Questions:
    Is the query important enough to justify special consideration?
    How many covering indexes?
    What is the performance impact of the new covering indexes on other queries?
    Query optimization:
    http://www.sqlusa.com/articles/query-optimization/
    Kalman Toth Database & OLAP Architect
    SELECT Video Tutorials 4 Hours
    New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

  • Bad performance with graphic glitches running intensive OpenCL software

    Under Yosemite Cinema 4D R16 (while R14 is works well) and Autocad for Mac 2015 (with all the previous releases) are affected by horizontal pixelated artifacts (not properly glitches by very near to be); and again iTunes library seems to be affected by horizontal portion of the library by the same glitch when you scroll down (it disappears after log out). Someone refers these issues to Vsync (that autodesk softwares make Off) while to me it seems clearly incompatibility drivers with Yosemite and last version of these softwares. My configuration is NVIDIA GeForce GTX 780M 4096 MB and mentioned softwares were fine under Mavericks and with the same Hardware... 

    There are currently two known operations that are seriously slower in update 10:
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6635462
    and
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6652116
    (taken from the release notes).
    You can disable the hardware pipeline to basically go back to the old situation as it was in update 7 if it is giving your problems. I wouldn't know why simple fill actions would be bogging it down though, it smells like something is done wrong in your app.

  • MBP Retina low performance with external displays

    Hi everyone!
    I have a very bad performance with my MBP 15´´ retina display when it comes to ad an external display. I have a FUL HD LG monitor that looks very bad when i connect the HDMI or the thunderbot port with the proper adapter (as bad as you can´t even read). I want to know if this may ba a hardware problem just with my computer or if it is a software problem, any ideas? does anyone have the same issue?
    How can i update my NVIDIA card???
    Thanks a lot!

    Topic seems to come up here often. Apple has a tendency to dismiss the issue.
    Its a pretty well known problem that Mac font smoothing doesn't seem to work well on high resolution third party external displays, making text hard to read. In addition, I think the Mac HDMI resolution support is limited to 1080p, so you must use DP or DVI video interfaces to see full monitor resolution.
    The OS default is no font smoothing on external displays (except perhaps the apple display). There is a terminal command that will enable font smoothing for any external monitor, but it often doesn't work well enough. I found that using the OS zoom feature magnifies text to the point to be easily readable. You can set zoom parameters in the accessibility systems preference panel.
    For some reason, sometimes the Mac OS thinks some monitors are TVs and use YCbCr instead of RGB. You can open the color sync utility and brouse the settings to see what is being used. There are scripts available that can fix that but are more complicated to install than an app.
    It seems that PCs are way ahead of Macs with external display implementation. Most folks having monitor problems with a Mac do not see the same issue with PCs or Unix/Linux OSs.
    Oh as far as updating the video card, can't. The monitor  "drivers" are built into the OS. When a new display is connected, the OS finds the profile for it.

  • Bad performance when deleting report column in webi(with "Design – Structure only")

    Hi all,
    One of our customer has recently upgraded from BO XI to BO4.1. In the new BO 4.1, they encountered a bad performance issue when they were deleting a column in Webi(using "Design – Structure only" mode).
    With “Design – Structure only" mode,  it took webi about 10 seconds to complete after the customer right-clicked a report column and clicked the "delete".  The customer said that they only need to wait for less than 1 second when they did the same in BO XI old version.
    The new BO version used is 4.1SP02, installed in Windows Server 2008 R2. (Server with 32 core CPU, 32G memory)
    This bad performance happened in both Webi web and Rich Client. (in Webi Rich Client, the performance is a little bit better. The 'delete column' action takes about 8 seconds to complete).
    Do anyone know how to tune this performance in webi?  Thank you.
    Besides, it seems that each time we are making change in the webi report structure in IE or Rich Client, webi need to interact with Server site to upload the changes. Is there any option to change this behavior?  Say, do not upload change to Server for when 'deleting report column', only trigger the upload after a set of actions(e.g. trigger when click the "Save" button).
    Thank you.
    Regards,
    Eton.

    Hi all,
    Could anyone help me on this?  Thanks!
    What customer concerns now is that when they did the same 'column editing' action in BO XI R2 for the same report, they did not need to wait.  And they need to wait for at least 7-8 second in the BO 4.1SP02 environment for this action to complete.(data already purged, in structure-only mode)
    One more information about the webi report being editing is: there are many sheets in the report(about 6~10 sheets in one report). Customer don't want to separate these sheet into different reports  as it will increase the effort of their end users to locate similar report sheets.
    Regards,
    Eton.

  • CMP 6.1 Entity bad performance.

    I'am using entity 1.1 EJB on WL 6.1 and facing very bad performances:
    around 150ms for an insert (i have 20 columns).
    When accessing an order interface to read 2 fields in a session bean method: around
    90 ms.
    I'am very disapointed and confused. What should I look up for
    to increase the performance ? Any important tuning or parameters ? Should I use EJB
    2.0 to have significant perf ?
    Thanks for any advice because we are thinking to switch all the application on stored
    procedures. A solution without Entity and fewer stateless session beans.
    My config:
    WL: 6.1 on Sun sparc
    SGBD: Sybase
    Entity: WebLogic 6.0.0 EJB 1.1 RDBMS (weblogic-rdbms11-persistence-600.dtd)
    Thanks

    Historically its hard to get good performance & scalability out of sybase
    without using stored procs. Using dynamic sql on sybase just doesnt do as
    well as procs. Oracle on the other hand can get very close to stored proc
    speed out of well written dynamic sql.
    As far as weblogic goes, my experience is the focus of their testing for db
    related stuff is Oracle, then DB2, then MSSQLServer. Sybase is usually last
    on the list.
    As far as the 6.1 cmp, haven't used it much, but because of these other
    things I would be cautious about using it with Sybase.
    Joel
    "Antoine Bas" <[email protected],> wrote in message
    news:3cc7cdcf$[email protected]..
    >
    I'am using entity 1.1 EJB on WL 6.1 and facing very bad performances:
    around 150ms for an insert (i have 20 columns).
    When accessing an order interface to read 2 fields in a session beanmethod: around
    90 ms.
    I'am very disapointed and confused. What should I look up for
    to increase the performance ? Any important tuning or parameters ? ShouldI use EJB
    2.0 to have significant perf ?
    Thanks for any advice because we are thinking to switch all theapplication on stored
    procedures. A solution without Entity and fewer stateless session beans.
    My config:
    WL: 6.1 on Sun sparc
    SGBD: Sybase
    Entity: WebLogic 6.0.0 EJB 1.1 RDBMS(weblogic-rdbms11-persistence-600.dtd)
    >
    Thanks

  • Performance with external display

    Hello,
    when I'm connecting my 19'' TFT to the MacBook the performance (with the same applications runnig) is realy bad. It tooks longer to switch between apps and if I don't use an app for some time, it can took up to 30 sec to "reactivate" the app.
    Because the HD is working when I switch apps, it looks like the OS is swapping. My question: Would it help to upgrade the MacBook to 2GB ram? AFAIC the intel card uses shared memory.
    Thanks for your help
    Till
    MacBook 1.83 GHz/1GB   Mac OS X (10.4.8)  

    How much RAM do you have? Remember that the MB does not have dedicated VRAM like some computers do and that it uses the system RAM to drive the graphics chipset.
    I use my MB with the mini-DVI to DVI adapter to drive a 20" widescreen monitor without any of the problems that you describe, but I have 2GB of RAM. If you only have the stock 512MB of RAM, that may be part of what you are seeing.

  • Bad performance when open a bi publisher report in excel

    We use bi publisher(xml publisher) to create a customized report. For a small report, user like it very much. But for a bigger report, users complain about the performance when they open the file.
    I know it is not a native excel file, that may cause the bad performance. So I ask my user to save it to a new file as a native excel format. The new file still worse than a normal excel file when we open it.
    I did a test. We try to save a bi publish report to excel format, the size shrink to 4Mb. But if we "copy all" and "Paste Special" value only to a new excel file, the size is only 1Mb.
    Do I have any way to improve that, users are complaining everyday. Thanks!
    I did a test today.
    I create a test report
    Test 1: Original file from BIP in EBS is 10Mb. We save it in my local disk, when we open the file, it takes 43 sec.
    Test 2: We save the file in native excel format, the file size is 2.28Mb, it takes 7 sec. to open.
    Test 3: We copy all cell and "PasteSpecial" to a new excel file with value only. The file size is 1.66Mb, it takes only 1 sec to open.
    Edited by: Rex Lin on 2010/3/31 下午 11:26

    EBS or Standalone BIP?
    If EBS see this thread for suggestions on performance tuning and hints and tips:
    EBS BIP Performance Tuning - Definitive Guide?
    Note also that I did end up rewriting my report as PL/SQL producing a csv file and have done with several large reports in BIP on EBS.
    Cheers,
    Dave

Maybe you are looking for

  • ITunes wont open Error -200

    yep well there i was opening iTunes and BLAMMO ! ITunes wont open error -200 what am i doing wrong now also coincedently my sound output aint working

  • Capacity Question -- How Do I Free Up More Space on my iPod Mini?

    The capacity of my iPod Mini is 3.79, and the capacity bar shows 3.74 GB attributable to Audio, 40.6 MB to Other, and 3.7 MB Free Space. I want to add playlists to this iPod, but I'm told I don't have enough space. I deleted several playlists from th

  • Air cs5 and template

    Hello, I'm trying to develop applications for Android. 1) I have the version of Flash included in Cs5 with solme litle examples of air, I need to download something else or air is already full? 2) there are some examples, on the web, of applications

  • Connector pane pattern bug

    LV2011, cant check other versions right now. The Connector pane pattern window doesn't mark/show your currently selected pattern. Not a big bug, but i still classify it as such. /Y LabVIEW 8.2 - 2014 "Only dead fish swim downstream" - "My life for Ku

  • PRT screen layout change in Work Order

    Hi  Experts , when we assogn PRT to an Operation in Maintenance order then PRT description by default comes in righ hand corner of the screen . I want to shift that column to near to PRT number . Can any one please help Thanks