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([email protected]!-500<[email protected]!-50)
   5 - access("SYS_SXI_0"."ORGANIZATION_ID"=6 AND "SYS_SXI_0"."IS_SENDER"=1 AND
              "SYS_SXI_0"."CREATION_TIME">[email protected]!-500 AND "SYS_SXI_0"."CREATION_TIME"<[email protected]!-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([email protected]!-500<[email protected]!-50)
  41 - access("SYS_SXI_0"."ORGANIZATION_ID"=6 AND "SYS_SXI_0"."IS_SENDER"=1 AND
              "SYS_SXI_0"."CREATION_TIME">[email protected]!-500 AND "SYS_SXI_0"."CREATION_TIME"<[email protected]!-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([email protected]!-500<[email protected]!-50)
  40 - access("SYS_SXI_0"."ORGANIZATION_ID"=6 AND "SYS_SXI_0"."IS_SENDER"=1 AND
              "SYS_SXI_0"."CREATION_TIME">[email protected]!-500 AND "SYS_SXI_0"."CREATION_TIME"<[email protected]!-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
              )>[email protected]!-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
              )<[email protected]!-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

Similar Messages

  • 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)

  • 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 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...

  • ABAP Select statement performance (with nested NOT IN selects)

    Hi Folks,
    I'm working on the ST module and am working with the document flow table VBFA. The query takes a large amount of time, and is timing out in production. I am hoping that someone would be able to give me a few tips to make this run faster. In our test environment, this query take 12+ minutes to process.
        SELECT vbfa~vbeln
               vbfa~vbelv
               Sub~vbelv
               Material~matnr
               Material~zzactshpdt
               Material~werks
               Customer~name1
               Customer~sortl
          FROM vbfa JOIN vbrk AS Parent ON ( Parentvbeln = vbfavbeln )
                 JOIN vbfa AS Sub ON ( Subvbeln = vbfavbeln )
                 JOIN vbap AS Material ON ( Materialvbeln = Subvbelv )
                 JOIN vbak AS Header ON ( Headervbeln = Subvbelv )
                 JOIN vbpa AS Partner ON ( Partnervbeln = Subvbelv )
                 JOIN kna1 AS Customer ON ( Customerkunnr = Partnerkunnr )
          INTO (WA_Transfers-vbeln,
                WA_Transfers-vbelv,
                WA_Transfers-order,
                WA_Transfers-MATNR,
                WA_Transfers-sdate,
                WA_Transfers-sfwerks,
                WA_Transfers-name1,
                WA_Transfers-stwerks)
          WHERE vbfa~vbtyp_n = 'M'       "Invoice
          AND vbfa~fktyp = 'L'           "Delivery Related Billing Doc
          AND vbfa~vbtyp_v = 'J'         "Delivery Doc
          AND vbfa~vbelv IN S_VBELV
          AND Sub~vbtyp_n = 'M'          "Invoice Document Type
          AND Sub~vbtyp_v = 'C'          "Order Document Type
          AND Partner~parvw = 'WE'       "Ship To Party(actual desc. is SH)
          AND Material~zzactshpdt IN S_SDATE
          AND ( Parentfkart = 'ZTRA' OR Parentfkart = 'ZTER' )
          AND vbfa~vbelv NOT IN
             ( SELECT subvbfa~vbelv
               FROM vbfa AS subvbfa
               WHERE subvbfavbelv = vbfavbelv
               AND   subvbfa~vbtyp_n = 'V' )           "Purchase Order
          AND vbfa~vbelv NOT IN
             ( SELECT DelList~vbeln
               FROM vbfa AS DelList
               WHERE DelListvbeln = vbfavbelv
               AND   DelList~vbtyp_v = 'C'             "Order Document Type
               AND   DelList~vbelv IN                  "Delivery Doc
                  ( SELECT OrderList~vbelv
                    FROM vbfa AS OrderList
                    WHERE OrderList~vbtyp_n = 'H' )    "Return Ord
          APPEND WA_Transfers TO ITAB_Transfers.
        ENDSELECT.
    Cheers,
    Chris

    I am sending u some of the performance isuues that are to be kept in mind while coding.
    1.Donot use Select *...... instead use Select <required list>......
    2.Donot fetch data from CLUSTER tables.
    3.Donot use Nested Select statements as. U have used nested select which reduces performance to a greater extent.
      Instead  use  views/join .
    Also keep in mind that not use join condition for more for more than three tables unless otherwise required.
    So split select statements into three or four and use Select ......for all entries....
    4.Extract  the data from the database  atonce consolidated upfront into table.
      i.e. use INTO TABLE <ITAB> clause instead of using
    Select----
    End Select.
    5.Never use order by clause in Select ..... statement. instead use SORT<itab>.
    6.When  ever u need to calculate max,min,avg,sum,count use AGGREGATE FUNCTIONS and GROUP BY clause insted of calculating by userself..
    7.Donot use the same table once for Validation and another time for data extraction.select data  only once.
    8.When the intention is for validation use Select single ....../Select.......up to one rows ......statements.
    9.If possible always use array operations to update the database tables.
    10.Order of the fields in the where clause select statement  must be in the same order in the index of table.
    11.Never release the object unless throughly checked by st05/se30/slin.
    12.Avoid using identical select statements.

  • 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

  • Creation of view with clob column in select and group by clause.

    Hi,
    We are trying to migrate a view from sql server2005 to oracle 10g. It has clob column which is used in group by clause. How can the same be achived in oracle 10g.
    Below is the sql statament used in creating view aling with its datatypes.
    CREATE OR REPLACE FORCE VIEW "TEST" ("CONTENT_ID", "TITLE", "KEYWORDS", "CONTENT", "ISPOPUP", "CREATED", "SEARCHSTARTDATE", "SEARCHENDDATE", "HITS", "TYPE", "CREATEDBY", "UPDATED", "ISDISPLAYED", "UPDATEDBY", "AVERAGERATING", "VOTES") AS
      SELECT content_ec.content_id,
              content_ec.title,
              content_ec.keywords,
              content_ec.content content ,
              content_ec.ispopup,
              content_ec.created,
              content_ec.searchstartdate,
              content_ec.searchenddate,
            COUNT(contenttracker_ec.contenttracker_id) hits,
              contenttypes_ec.type,
              users_ec_1.username createdby,
              Backup_Latest.created updated,
              Backup_Latest.isdisplayed,
              users_ec_1.username updatedby,
              guideratings.averagerating,
              guideratings.votes
         FROM users_ec users_ec_1
                JOIN Backup_Latest
                 ON users_ec_1.USER_ID = Backup_Latest.USER_ID
                RIGHT JOIN content_ec
                JOIN contenttypes_ec
                 ON content_ec.contenttype_id = contenttypes_ec.contenttype_id
                 ON Backup_Latest.content_id = content_ec.content_id
                LEFT JOIN guideratings
                 ON content_ec.content_id = guideratings.content_id
                LEFT JOIN contenttracker_ec
                 ON content_ec.content_id = contenttracker_ec.content_id
                LEFT JOIN users_ec users_ec_2
                 ON content_ec.user_id = users_ec_2.USER_ID
         GROUP BY content_ec.content_id,
         content_ec.title,
         content_ec.keywords,
         to_char(content_ec.content) ,
         content_ec.ispopup,
         content_ec.created,
         content_ec.searchstartdate,
         content_ec.searchenddate,
         contenttypes_ec.type,
         users_ec_1.username,
         Backup_Latest.created,
         Backup_Latest.isdisplayed,
         users_ec_1.username,
         guideratings.averagerating,
         guideratings.votes;
    Column Name      Data TYpe
    CONTENT_ID     NUMBER(10,0)
    TITLE          VARCHAR2(50)
    KEYWORDS     VARCHAR2(100)
    CONTENT          CLOB
    ISPOPUP          NUMBER(1,0)
    CREATED          TIMESTAMP(6)
    SEARCHSTARTDATE     TIMESTAMP(6)
    SEARCHENDDATE     TIMESTAMP(6)
    HITS          NUMBER
    TYPE          VARCHAR2(50)
    CREATEDBY     VARCHAR2(20)
    UPDATED          TIMESTAMP(6)
    ISDISPLAYED     NUMBER(1,0)
    UPDATEDBY     VARCHAR2(20)
    AVERAGERATING     NUMBER
    VOTES          NUMBERAny help realyy appreciated.
    Thanks in advance
    Edited by: user512743 on Dec 10, 2008 10:46 PM

    Hello,
    Specifically, this should be asked in the
    ASP.Net MVC forum on forums.asp.net.
    Karl
    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
    My Blog: Unlock PowerShell
    My Book: Windows PowerShell 2.0 Bible
    My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

  • 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 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

  • Can i change the behavior of the character menu so that the list begins with the current font selected and not at the beginning of the list?

    Im struggling with the way the font selection tab works in the character menu.
    When i scroll down the list and select minion halfway down the list, the next time i click on the font tab, the list starts back at the top of the list making me scroll down the list every time i want to look for a font.
    Can anyone offer some suggestions here?
    thanks
    jeff

    You can't do it exactly the way you want, but if you have InDesign CC or CC 2014, you can set fonts in the Character panel or Control panel Type menu to be Favorites. Click the "star" beside a font to set it as a favorite. Then at the top of the menu, click the "star" filter to show favorites in your list instead of a list of all the fonts.

  • 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.

  • 6500 performance with mix of PFC3BXL, DFC3CXL and CFC modules

    Am looking at a 6500 which has WS-SUP720-3BXL and WS-X6708 with DFC3 CXL.
    It also has 5x 6748 cards with CFC installed.
    If I check the platform mode its 3BXL, as its fallen back to the module fitted to the SUP720.
    As this switch also has some line cards fitted with CFC's what is the total system forwarding capability?
    Is it 30Mpps for all 5 of the 6748/CFC cards and a higher rate for the WS-SUP720-3BXL and WS-X6708, or 30Mpps across the whole system?
    Initially I understood it to be 30Mpps across all slots, regardless of cards and modules fitted if a CFC existed in the chassis.
    After reading several architecture documents now I'm not so sure it is that simple.

    Disclaimer
    The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
    Liability Disclaimer
    In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
    Posting
    Traffic ingressing on a non-DFC card will use (and share) the sup's Mpps.
    Traffic ingress on a DFC card will use the card's DFC Mpps.
    Traffic egressing on either card, has already used the PPS of the ingress.
    "All the links in the Cisco Virtual Switching Supervisor Engine 720 can be active simultaneously even in the redundant configurations, thereby increasing the supervisor throughput from 48 to 82 Mpps."
    I.e. 48 Mpps since sup, 82 Mpps with 2nd sup.
    BTW, the sup2T offers even more single sup PPS, 60 (?) Mpps.
    You might find this of interest: http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/107258-C6K-PFC-DFC-CFC.html

  • 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.

  • 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.

Maybe you are looking for