Response time of Structure event & simultaneous execution of events

Hello. I built a VI using the structure of the event. Whenever I press a button to start the program (for example, I press "w" to the throttle), the indicator does not respond immediately. Is it normal for the structures of the event or can I do? Another problem I have is when I am pressing on a button, I can not press other buttons to work simultaneously (for example, I press "w" to the throttle and yaw "d"). Is there a way I can change this? Please advice.

Thank you

Hello

Watch what you do with these business structures.

Better, you can use in the range and force.

Already done this for you well, there's also a better way to come of age this another case structure on the right.

You had no timeout in the structure of the event, so he'd be stuck in this case.

As its name suggests doesn't work if the key is down for a little while has added another key case down, repeat.

I found something strange to the w, a, s, d keys allow you to the stored value but with to the up, down, left, right you set back to 0 after releasing.

Koen

Tags: NI Software

Similar Questions

JKI event response time

Hello

I discovered jki awhile but, never had the opportunity to use it. Today I'm trying to see how it works

but I'm having problems when the task are back on themselves a mount of idle time is not attentive

before the end of this taks: for example waiting for an instrument prior to prepare you.

Its there a way to have a response time of more short UI

here a basic example of 8,6 it could takes between 0 to 3 s to stop

Best regards

Tinnitus

I often force them to pass through a State of rest when I'm waiting like this. It has been discussed on the forum JKI here. You will need to use a time-out value<= 0="" for="" this="" to="">

Improves the response time

Here's my current situation. I'm in MARCH the version 4.2.1 of the application I have a test environment 1-2821 router with IPS version of the module 12.4 T, 1-2621 router with net stream is running version 12.2, OS 1-2950 switch and a stand alone server MARCH. When I run the script to test the response time (the time it takes MARCH to warn me of the attack) it takes anywhere from 1/2 hour and 1 hour before the alarm appears where the dashboard is a way to improve the response time? Second, I see the IPS signatures in the syslog, but I don't see them on my request of MARCH during investigations into an attack. If I run a query for real-time, I see everything but cannot investigate the attack.

I wonder the usefulness of a VINE if you are not running the latest version of the software. Cisco is expected to provide the latest update for you. The question of the DST, for example, causing some of the major problems for us.

Run a real-time event query to determine if the events you generate are 'collected' immediately. If they are, what are the events? What rule expect you fire? Here is a description of the rules should work (they should take immediately before the start of any limitation).

http://ciscomars.blogspot.com/2007/02/guest-article-Mars-inspection-rule.html

Subquery Factoring - cardinality estimate good but bad sql response times

This is Exadata 11.2.0.4.0 database, all tables have statistics of up to date. Cardinality estimation is good compared to the actual cardinality. It is a way to tune this sql to reduce its response time.
Sorry for the long sql and the execution plan.
```
WITH SUBWITH0 AS
  (SELECT D1.c1 AS c1
  FROM (
    (SELECT D1.c1 AS c1
    FROM
      (SELECT DISTINCT T7171.CH_ID_SYM AS c1
      FROM DW.TM_R_REP T7171
      WHERE ( T7171.CHILD_REP_ID = 939 )
      ) D1
    UNION
    SELECT D1.c1 AS c1
    FROM
      (SELECT DISTINCT T7167.MEMBER_KEY_SYM AS c1
      FROM DW.PC_T_REP T7167
      WHERE ( T7167.ANCESTOR_KEY = 939 )
      ) D1
    ) ) D1
  ),
  SUBWITH1 AS
  (SELECT D1.c1 AS c1
  FROM (
    (SELECT D1.c1 AS c1
    FROM
      (SELECT DISTINCT T7171.CH_ID_SYM AS c1
      FROM DW.TM_R_REP T7171
      WHERE ( T7171.CHILD_REP_ID = 939 )
      ) D1
    UNION
    SELECT D1.c1 AS c1
    FROM
      (SELECT DISTINCT T7167.MEMBER_KEY_SYM AS c1
      FROM DW.PC_T_REP T7167
      WHERE ( T7167.ANCESTOR_KEY = 939 )
      ) D1
    ) ) D1
  ),
  SUBWITH2 AS
  (SELECT DISTINCT T7171.CH_ID_SYM AS c1
  FROM ( DW.PC_T_REP T7167
  LEFT OUTER JOIN DW.TM_R_REP T7171
  ON T7167.ANCESTOR_KEY    = T7171.CHILD_REP_ID
  AND T7167.SALESYEARMONTH = T7171.SALES_YEAR_MONTH)
  LEFT OUTER JOIN DW.TM_REP T6715
  ON T7171.CHILD_REP_ID_N = T6715.REP_ID
  WHERE (
    CASE
      WHEN T7171.CHILD_REP_ID_N LIKE '9999%'
      THEN concat(concat('UNASSIGNED', lpad(' ', 2)), CAST(T7167.TERRITORY_ID AS VARCHAR ( 20 ) ))
      ELSE concat(concat(concat(concat(T6715.FIRST_NAME, lpad(' ', 2)), T6715.MIDDLE_NAME), lpad(' ', 2)), T6715.LAST_NAME)
    END = 'JOES     CRAMER'
  AND T7171.SALES_YEAR_MONTH BETWEEN '201505' AND '201505'
  AND T7171.CH_ID_SYM IN
    (SELECT DISTINCT D1.c1 AS c1 FROM SUBWITH0 D1
    ) )
  ),
  SUBWITH3 AS
  (SELECT MEMBER_KEY_SYM AS c1
  FROM DW.PC_T_REP T7167
  WHERE ( IS_LEAF = 1 )
  ),
  SAWITH0 AS
  (SELECT DISTINCT
    CASE
      WHEN T7171.CHILD_REP_ID_N LIKE '9999%'
      THEN concat(concat('UNASSIGNED', lpad(' ', 2)), CAST(T7167.TERRITORY_ID AS VARCHAR ( 20 ) ))
      ELSE concat(concat(concat(concat(T6715.FIRST_NAME, lpad(' ', 2)), T6715.MIDDLE_NAME), lpad(' ', 2)), T6715.LAST_NAME)
    END                      AS c1,
    T6715.REP_NUM          AS c2,
    T7171.SALES_YEAR_MONTH AS c3,
    T7315.MONTH_NUMERIC    AS c4,
    CASE
      WHEN T7171.CH_ID_SYM IN
        (SELECT D1.c1 AS c1
        FROM SUBWITH3 D1
        )
      THEN 1
      ELSE 0
    END                                              AS c5,
    CAST(T7171.PARENT_REP_ID AS CHARACTER ( 30 ) ) AS c6,
    T7171.CH_ID_SYM                         AS c7,
    T7171.PARENT_REP_ID_SYM                        AS c8
  FROM DW.TIM_MON T7315
    ,
    ( ( DW.PC_T_REP T7167
  LEFT OUTER JOIN (
    (SELECT TO_NUMBER(TO_CHAR(L_OPP.CloseDate,'YYYYMM')) AS Sales_Year_Month,
      Tm_Rep.Rep_Id                                              AS Rep_Id,
      L_OPP.Account_Name__C                              AS Account_Name__C,
      L_OPP.Closedate                                    AS Closedate,
      L_OPP.Forecastcategory                             AS Forecastcategory,
      L_OPP.Forecastcategoryname                         AS Forecastcategoryname,
      L_User.NAME                                                AS Opp_Owner_S_Sales_Org__C,
      L_OPP.Opportunity_Id__C                            AS Opportunity_Id__C,
      L_OPP.Renewal_Date__C                              AS Renewal_Date__C,
      L_OPP.Total_Incremental__C                         AS Total_Incremental__C,
      L_OPP.Offer_Code__C                                AS Offer_Code__C,
      L_OPP.ID                                           AS Opportunity_ID,
      L_OPP.TERRITORYID                                  AS TERRITORYID,
      L_OPP.ACCOUNTID                                    AS ACCOUNTID,
      L_OPP.OWNERID                                      AS OWNERID,
      L_OPP.TOTAL_RENEWAL__C                             AS TOTAL_RENEWAL__C,
      L_OPP.NAME                                         AS NAME,
      L_OPP.STAGENAME                                    AS STAGE_NAME,
      L_OPP.STAGE_DESCRIPTION__C                         AS STAGE_DESCRIPTION,
      NVL(
      CASE
        WHEN L_OPP.Forecastcategory                = 'Closed'
        AND( OPP_C_DIM.OPPORTUNITIES_GROUP IS NULL )
        THEN L_OPP.Total_Incremental__C
      END , 0) AS Closed_Oppurtunity,
      CASE
        WHEN L_OPP.Forecastcategory                 = 'Closed'
        AND ( OPP_C_DIM.OPPORTUNITIES_GROUP IS NULL )
        THEN 'Closed_Oppurtunity_Drill'
      END AS Closed_Oppurtunity_Drill,
      NVL(
      CASE
        WHEN L_OPP.Forecastcategoryname            IN ('Pipeline', 'Potential', 'Commit')
        AND ( OPP_C_DIM.OPPORTUNITIES_GROUP IS NULL )
        THEN L_OPP.Total_Incremental__C
      END , 0) AS OPEN_Oppurtunity,
      CASE
        WHEN L_OPP.Forecastcategoryname            IN ('Pipeline', 'Potential', 'Commit')
        AND ( OPP_C_DIM.OPPORTUNITIES_GROUP IS NULL )
        THEN 'OPEN_Oppurtunity_Drill'
      END AS OPEN_Oppurtunity_Drill,
      NVL(
      CASE
        WHEN L_OPP.Forecastcategory              = 'Closed'
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL1'
        THEN L_OPP.TOTAL_RENEWAL__C
      END , 0) AS Renewal_Year1_Closed_Opp,
      CASE
        WHEN L_OPP.Forecastcategory              = 'Closed'
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL1'
        THEN 'Renewal_Year1_Closed_Opp_Drill'
      END AS Renewal_Year1_Closed_Opp_Drill,
      NVL(
      CASE
        WHEN L_OPP.Forecastcategory             IN ('Pipeline', 'Forecast', 'BestCase')
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL1'
        THEN L_OPP.TOTAL_RENEWAL__C
      END , 0) AS Renewal_Year1_OPEN_Opp,
      CASE
        WHEN L_OPP.Forecastcategory             IN ('Pipeline', 'Forecast', 'BestCase')
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL1'
        THEN 'Renewal_Year1_OPEN_Opp_Drill'
      END AS Renewal_Year1_OPEN_Opp_Drill,
      NVL(
      CASE
        WHEN L_OPP.Forecastcategory              = 'Closed'
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL2'
        THEN L_OPP.TOTAL_RENEWAL__C
      END , 0) AS Renewal_Year2_Closed_Opp,
      CASE
        WHEN L_OPP.Forecastcategory              = 'Closed'
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL2'
        THEN 'Renewal_Year2_Closed_Opp_Drill'
      END AS Renewal_Year2_Closed_Opp_Drill,
      NVL(
      CASE
        WHEN L_OPP.Forecastcategory             IN ('Pipeline', 'Forecast', 'BestCase')
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL2'
        THEN L_OPP.TOTAL_RENEWAL__C
      END , 0) AS Renewal_Year2_OPEN_Opp,
      CASE
        WHEN L_OPP.Forecastcategory             IN ('Pipeline', 'Forecast', 'BestCase')
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL2'
        THEN 'Renewal_Year2_OPEN_Opp_Drill'
      END AS Renewal_Year2_OPEN_Opp_Drill
    FROM DW.OPP_C_DIM
    RIGHT OUTER JOIN RT.L_OPP
    ON (TO_CHAR(OPP_C_DIM.OFFER_CODE) =TO_CHAR(L_OPP.Offer_Code__C)
    AND (TO_CHAR(L_OPP.CloseDate,'YYYYMM'))  = TO_CHAR(OPP_C_DIM.PERIOD))
    LEFT OUTER JOIN RT.L_User
    ON (L_OPP.Ownerid=L_User.Id)
    LEFT OUTER JOIN DW.Tm_Rep
    ON (Tm_Rep.Rep_Num='0'
      ||L_User.Rep_Employee_Number__C)
    )) T774110 ON T7167.MEMBER_KEY = T774110.Rep_Id
  AND T7167.SALESYEARMONTH         = T774110.Sales_Year_Month)
  LEFT OUTER JOIN DW.TM_R_REP T7171
  ON T7167.ANCESTOR_KEY    = T7171.CHILD_REP_ID
  AND T7167.SALESYEARMONTH = T7171.SALES_YEAR_MONTH)
  LEFT OUTER JOIN DW.TM_REP T6715
  ON T7171.CHILD_REP_ID_N        = T6715.REP_ID
  WHERE ( T774110.Sales_Year_Month = T7315.YEAR_MONTH
  AND T7171.CH_ID_SYM    IN
    (SELECT DISTINCT D1.c1 AS c1 FROM SUBWITH2 D1
    )
  AND T7171.SALES_YEAR_MONTH BETWEEN '201505' AND '201505'
  AND T7171.CH_ID_SYM IN
    (SELECT DISTINCT D1.c1 AS c1 FROM SUBWITH1 D1
    ) )
  ),
  SAWITH1 AS
  (SELECT SUM(T774110.Renewal_Year2_OPEN_Opp) AS c9,
    SUM(T774110.Renewal_Year2_Closed_Opp)     AS c10,
    SUM(T774110.Renewal_Year1_OPEN_Opp)       AS c11,
    SUM(T774110.Renewal_Year1_Closed_Opp)     AS c12,
    SUM(T774110.OPEN_Oppurtunity)             AS c13,
    SUM(T774110.Closed_Oppurtunity)           AS c14,
    T7315.MONTH_NUMERIC                     AS c15,
    T7171.CH_ID_SYM                  AS c16
  FROM DW.TIM_MON T7315
    ,
    ( RT.L_ACCOUNT T765190
  LEFT OUTER JOIN ( DW.PC_T_REP T7167
  LEFT OUTER JOIN (
    (SELECT TO_NUMBER(TO_CHAR(L_OPP.CloseDate,'YYYYMM')) AS Sales_Year_Month,
      Tm_Rep.Rep_Id                                              AS Rep_Id,
      L_OPP.Account_Name__C                              AS Account_Name__C,
      L_OPP.Closedate                                    AS Closedate,
      L_OPP.Forecastcategory                             AS Forecastcategory,
      L_OPP.Forecastcategoryname                         AS Forecastcategoryname,
      L_User.NAME                                                AS Opp_Owner_S_Sales_Org__C,
      L_OPP.Opportunity_Id__C                            AS Opportunity_Id__C,
      L_OPP.Renewal_Date__C                              AS Renewal_Date__C,
      L_OPP.Total_Incremental__C                         AS Total_Incremental__C,
      L_OPP.Offer_Code__C                                AS Offer_Code__C,
      L_OPP.ID                                           AS Opportunity_ID,
      L_OPP.TERRITORYID                                  AS TERRITORYID,
      L_OPP.ACCOUNTID                                    AS ACCOUNTID,
      L_OPP.OWNERID                                      AS OWNERID,
      L_OPP.TOTAL_RENEWAL__C                             AS TOTAL_RENEWAL__C,
      L_OPP.NAME                                         AS NAME,
      L_OPP.STAGENAME                                    AS STAGE_NAME,
      L_OPP.STAGE_DESCRIPTION__C                         AS STAGE_DESCRIPTION,
      NVL(
      CASE
        WHEN L_OPP.Forecastcategory                = 'Closed'
        AND( OPP_C_DIM.OPPORTUNITIES_GROUP IS NULL )
        THEN L_OPP.Total_Incremental__C
      END , 0) AS Closed_Oppurtunity,
      CASE
        WHEN L_OPP.Forecastcategory                 = 'Closed'
        AND ( OPP_C_DIM.OPPORTUNITIES_GROUP IS NULL )
        THEN 'Closed_Oppurtunity_Drill'
      END AS Closed_Oppurtunity_Drill,
      NVL(
      CASE
        WHEN L_OPP.Forecastcategoryname            IN ('Pipeline', 'Potential', 'Commit')
        AND ( OPP_C_DIM.OPPORTUNITIES_GROUP IS NULL )
        THEN L_OPP.Total_Incremental__C
      END , 0) AS OPEN_Oppurtunity,
      CASE
        WHEN L_OPP.Forecastcategoryname            IN ('Pipeline', 'Potential', 'Commit')
        AND ( OPP_C_DIM.OPPORTUNITIES_GROUP IS NULL )
        THEN 'OPEN_Oppurtunity_Drill'
      END AS OPEN_Oppurtunity_Drill,
      NVL(
      CASE
        WHEN L_OPP.Forecastcategory              = 'Closed'
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL1'
        THEN L_OPP.TOTAL_RENEWAL__C
      END , 0) AS Renewal_Year1_Closed_Opp,
      CASE
        WHEN L_OPP.Forecastcategory              = 'Closed'
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL1'
        THEN 'Renewal_Year1_Closed_Opp_Drill'
      END AS Renewal_Year1_Closed_Opp_Drill,
      NVL(
      CASE
        WHEN L_OPP.Forecastcategory             IN ('Pipeline', 'Forecast', 'BestCase')
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL1'
        THEN L_OPP.TOTAL_RENEWAL__C
      END , 0) AS Renewal_Year1_OPEN_Opp,
      CASE
        WHEN L_OPP.Forecastcategory             IN ('Pipeline', 'Forecast', 'BestCase')
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL1'
        THEN 'Renewal_Year1_OPEN_Opp_Drill'
      END AS Renewal_Year1_OPEN_Opp_Drill,
      NVL(
      CASE
        WHEN L_OPP.Forecastcategory              = 'Closed'
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL2'
        THEN L_OPP.TOTAL_RENEWAL__C
      END , 0) AS Renewal_Year2_Closed_Opp,
      CASE
        WHEN L_OPP.Forecastcategory              = 'Closed'
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL2'
        THEN 'Renewal_Year2_Closed_Opp_Drill'
      END AS Renewal_Year2_Closed_Opp_Drill,
      NVL(
      CASE
        WHEN L_OPP.Forecastcategory             IN ('Pipeline', 'Forecast', 'BestCase')
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL2'
        THEN L_OPP.TOTAL_RENEWAL__C
      END , 0) AS Renewal_Year2_OPEN_Opp,
      CASE
        WHEN L_OPP.Forecastcategory             IN ('Pipeline', 'Forecast', 'BestCase')
        AND OPP_C_DIM.OPPORTUNITIES_GROUP ='RENEWAL2'
        THEN 'Renewal_Year2_OPEN_Opp_Drill'
      END AS Renewal_Year2_OPEN_Opp_Drill
    FROM DW.OPP_C_DIM
    RIGHT OUTER JOIN RT.L_OPP
    ON (TO_CHAR(OPP_C_DIM.OFFER_CODE) =TO_CHAR(L_OPP.Offer_Code__C)
    AND (TO_CHAR(L_OPP.CloseDate,'YYYYMM'))  = TO_CHAR(OPP_C_DIM.PERIOD))
    LEFT OUTER JOIN RT.L_User
    ON (L_OPP.Ownerid=L_User.Id)
    LEFT OUTER JOIN DW.Tm_Rep
    ON (Tm_Rep.Rep_Num='0'
      ||L_User.Rep_Employee_Number__C)
    )) T774110 ON T7167.MEMBER_KEY = T774110.Rep_Id
  AND T7167.SALESYEARMONTH         = T774110.Sales_Year_Month) ON T765190.ID = T774110.ACCOUNTID)
  LEFT OUTER JOIN DW.TM_R_REP T7171
  ON T7167.ANCESTOR_KEY          = T7171.CHILD_REP_ID
  AND T7167.SALESYEARMONTH       = T7171.SALES_YEAR_MONTH
  WHERE ( T774110.Sales_Year_Month = T7315.YEAR_MONTH
  AND T7171.CH_ID_SYM    IN
    (SELECT DISTINCT D1.c1 AS c1 FROM SUBWITH2 D1
    )
  AND T7171.SALES_YEAR_MONTH BETWEEN '201505' AND '201505'
  AND T7171.CH_ID_SYM IN
    (SELECT DISTINCT D1.c1 AS c1 FROM SUBWITH1 D1
    ) )
  GROUP BY T7171.CH_ID_SYM,
    T7315.MONTH_NUMERIC
  )
SELECT DISTINCT D2.c9 AS c1,
  D2.c10              AS c2,
  D2.c11              AS c3,
  D2.c12              AS c4,
  D2.c13              AS c5,
  D2.c14              AS c6,
  D1.c1               AS c7,
  D1.c2               AS c8,
  D1.c3               AS c9,
  D1.c4               AS c10,
  D1.c5               AS c11,
  D1.c6               AS c12,
  D1.c7               AS c13,
  D1.c8               AS c14
FROM SAWITH0 D1
INNER JOIN SAWITH1 D2
ON SYS_OP_MAP_NONNULL(D2.c15)  = SYS_OP_MAP_NONNULL(D1.c4)
AND SYS_OP_MAP_NONNULL(D2.c16) = SYS_OP_MAP_NONNULL(D1.c7)
ORDER BY c10,
  c13
```
SQL in real time, followed by the details with the Predicate Section of dbms_xplan.display_cursor shot
Global stats
==============================================================================================================================
| Elapsed.   CPU |    E/S | Request | Cluster | Others | Pick up | Buffer | Read | Read | Write | Write | Cell |
| Time (s) | Time (s) | Waiting (s) | Waiting (s) | Waiting (s) | Waiting (s) | Calls | Gets | Reqs | Bytes | Reqs | Bytes | Unloading |
==============================================================================================================================
|     152.     146.     3.73 |        0.08 |     0.04 |     2.04 |     2.    16 M | 5223.   1 GB |     1. 200KB | 95,11% |
==============================================================================================================================
SQL details surveillance Plan (Plan hash value = 442312180)
===============================================================================================================================================================================================================================================
| ID |                          Operation |            Name | Lines | Cost |   Time | Start | Execs |   Lines | Read | Read | Cell | MEM | Activity |         Activity detail |
|    |                                                              |                             | (Estimated) |       | Active (s) | Active |       | (Real) | Reqs | Bytes | Unloading | (Max) |   (%)    |           (Number of samples).
===============================================================================================================================================================================================================================================
| 0 | SELECT STATEMENT |                             |         |       |         1.   152.     1.        0 |      |       |         |       |     0.65 | Cpu (1)                            |
| 1.   RANGE OF PARTITION ALL THE |                             |       1. 3892 |           |        |     1.          |      |       |         |       |          |                                    |
| 2.    ACCESS STORAGE FULL FIRST RANKS TABLE. PC_T_REP |       1. 3892 |           |        |    37.          |   74. 19 MB | 78.45% |   17 M |          |                                    |
| 3.   TRANSFORMATION OF THE TEMPORARY TABLE.                             |         |       |         1.   152.     1.        1.      |       |         |       |          |                                    |
| 4.    LOAD SELECT ACE |                             |         |       |         1.     + 5 |     1.        1.      |       |         | 278K |          |                                    |
| 5.     VIEW                                                     |                             |     105. 3980 |         1.     + 5 |     1.    13637 |      |       |         |       |          |                                    |
| 6.      SORT UNIQUE                                             |                             |     105. 3980 |         1.     + 5 |     1.    13637 |      |       |         | 757K |          |                                    |
| 7.       UNION-ALL                                              |                             |         |       |         1.     + 5 |     1.    14033.      |       |         |       |          |                                    |
| 8.        STORE TABLE FULL ACCESS | TM_R_REP |      22.    88.         1.     + 5 |     1.       36.      |       |         |       |          |                                    |
| 9.        RANGE OF PARTITION ALL THE |                             |      83. 3890.         1.     + 5 |     1.    13997.      |       |         |       |          |                                    |
| 10.         STORE TABLE FULL ACCESS | PC_T_REP |      83. 3890.         6.     + 0 |    37.    13997.      |       |         |    2 M |     0.65 | Smart cell table scan (1) |
| 11.    LOAD SELECT ACE |                             |         |       |         1.     + 5 |     1.        1.      |       |         | 278K |          |                                    |
| 12.     HASH UNIQUE                                              |                             |       1. 4166.         1.     + 5 |     1.        1.      |       |         | 479K |          |                                    |
| 13.      HASH JOIN                                               |                             |       1. 4165 |         1.     + 5 |     1.      444.      |       |         |    1 M |          |                                    |
| 14.       JOIN FILTER PART CREATE | : BF0000 |       3. 4075 |         1.     + 5 |     1.      549.      |       |         |       |          |                                    |
| 15.        OUTER HASH JOIN |                             |       3. 4075 |         1.     + 5 |     1.      549.      |       |         |    1 M |          |                                    |
| 16.         HASH JOIN                                            |                             |       3. 4068 |         1.     + 5 |     1.      549.      |       |         |    2 M |          |                                    |
| 17.          VIEW                                                |                             |     105. 3980 |         1.     + 5 |     1.    13637 |      |       |         |       |          |                                    |
| 18.           SORT UNIQUE                                        |                             |     105. 3980 |         1.     + 5 |     1.    13637 |      |       |         | 757K |          |                                    |
| 19.            UNION-ALL                                         |                             |         |       |         1.     + 5 |     1.    14033.      |       |         |       |          |                                    |
| 20.             STORE TABLE FULL ACCESS | TM_R_REP |      22.    88.         1.     + 5 |     1.       36.      |       |         |       |          |                                    |
| 21.             RANGE OF PARTITION ALL THE |                             |      83. 3890.         1.     + 5 |     1.    13997.      |       |         |       |          |                                    |
| 22.              STORE TABLE FULL ACCESS | PC_T_REP |      83. 3890.         1.     + 5 |    37.    13997.      |       |         |    2 M |          |                                    |
| 23.          STORE TABLE FULL ACCESS | TM_R_REP |    1884 |    88.         1.     + 5 |     1.     1929 |      |       |         |       |          |                                    |
| 24.         STORE TABLE FULL ACCESS | TM_REP                      |    7136 |     7.         1.     + 5 |     1.     7137 |      |       |         |       |          |                                    |
| 25.       RANGE OF SINGLE PARTITION |                             |    7449.    90.         1.     + 5 |     1.     7449.      |       |         |       |          |                                    |
| 26.        STORE TABLE FULL ACCESS | PC_T_REP |    7449.    90.         1.     + 5 |     1.     7449.      |       |         |       |          |                                    |
| 27.    SORT UNIQUE                                               |                             |       1. 26032 |         1.   152.     1.        1.      |       |         | 2048 |          |                                    |
| 28.     OUTER HASH JOIN |                             |       1. 26031 |        72.    + 81 |     1.     8238 |      |       |         |    4 M |          |                                    |
| 29.      FILTER                                                  |                             |         |       |        74.    + 79 |     1.     8238 |      |       |         |       |     1.96 | Cpu (3)                            |
| 30.       NESTED EXTERNAL LOOPS |                             |       1. 26027 |        72.    + 81 |     1.      15 M |      |       |         |       |     3.27 | Cpu (5)                            |
| 31.        HASH JOIN                                             |                             |       1. 26026 |        72.    + 81 |     1.      15 M |      |       |         | 447K |    18.95 | Cpu (29)                           |
| 32.         OUTER HASH JOIN |                             |       1. 13213 |         1.    + 81 |     1.      332.      |       |         | 452K |          |                                    |
| 33.          HASH JOIN                                           |                             |       1. 13206 |         1.    + 81 |     1.      332.      |       |         |    1 M |          |                                    |
| 34.           HASH JOIN                                          |                             |       1. 13199.         1.    + 81 |     1.      444.      |       |         | 434K |          |                                    |
| 35.            HASH JOIN                                         |                             |       1. 13197.         1.    + 81 |     1.      444.      |       |         | 290K |          |                                    |
| 36.             JOIN CREATE FILTER | : BF0000 |       1. 13195.         1.    + 81 |     1.      444.      |       |         |       |          |                                    |
| 37.              HASH JOIN                                       |                             |       1. 13195.         1.    + 81 |     1.      444.      |       |         |    2 M |          |                                    |
| 38.               THE CARTESIAN MERGE JOIN.                             |      27. 13107 |         1.    + 81 |     1.     7449.      |       |         |       |          |                                    |
| 39.                HASH JOIN                                     |                             |       1. 13017.        77.     + 5 |     1.        1.      |       |         | 750K |          |                                    |
| 40.                 STORE TABLE FULL ACCESS | TIM_MON |       1.     4.         1.     + 5 |     1.        1.      |       |         |       |          |                                    |
| 41.                 VIEW                                         |                             |       1. 13013.         1.    + 81 |     1.        1.      |       |         |       |          |                                    |
| 42.                  HASH GROUP BY.                             |       1. 13013.         1.    + 81 |     1.        1.      |       |         | 482K |          |                                    |
| 43.                   OUTER HASH JOIN |                             |       1. 13012.        77.     + 5 |     1.     8238 |      |       |         |    4 M |          |                                    |
| 44.                    NESTED LOOPS |                             |       1. 13008.        77.     + 5 |     1.     8238 |      |       |         |       |          |                                    |
| 45.                     FILTER                                   |                             |         |       |        77.     + 5 |     1.     8238 |      |       |         |       |     2.61 | Cpu (4)                            |
| 46.                      NESTED EXTERNAL LOOPS |                             |       1. 13007.        77.     + 5 |     1.      15 M |      |       |         |       |     4.58. Cpu (7)                            |
| 47.                       HASH JOIN                              |                             |       1. 13006.        77.     + 5 |     1.      15 M |      |       |         | 424K |    11.76. Cpu (18)                           |
| 48.                        HASH JOIN |                             |       1.   193.         1.     + 5 |     1.      332.      |       |         |    1 M |          |                                    |
| 49.                         HASH JOIN |                             |       1.   186.         1.     + 5 |     1.      444.      |       |         | 420K |          |                                    |
| 50.                          HASH JOIN |                             |       4.   184.         1.     + 5 |     1.      444.      |       |         | 290K |          |                                    |
| 51.                           JOIN CREATE FILTER | : BF0002 |       1.    94.         1.     + 5 |     1.        1.      |       |         |       |          |                                    |
| 52.                            JOIN FILTER PART CREATE | : BF0001 |       1.    94.         1.     + 5 |     1.        1.      |       |         |       |          |                                    |
| 53.                             HASH JOIN |                             |       1.    94.         1.     + 5 |     1.        1.      |       |         | 290K |          |                                    |
| 54.                              JOIN CREATE FILTER | : BF0003 |       1.     6.         1.     + 5 |     1.        1.      |       |         |       |          |                                    |
| 55.                               THE CARTESIAN MERGE JOIN.                             |       1.     6.         1.     + 5 |     1.        1.      |       |         |       |          |                                    |
| 56.                                STORE TABLE FULL ACCESS | TIM_MON |       1.     4.         1.     + 5 |     1.        1.      |       |         |       |          |                                    |
| 57.                                KIND OF BUFFER.                             |       1.     2.         1.     + 5 |     1.        1.      |       |         | 2048 |          |                                    |
| 58.                                 VIEW                         | VW_NSO_1 |       1.     2.         1.     + 5 |     1.        1.      |       |         |       |          |                                    |
| 59.                                  UNIQUE HASH |                             |       1.       |         1.     + 5 |     1.        1.      |       |         | 485K |          |                                    |
| 60.                                   VIEW                       |                             |       1.     2.         1.     + 5 |     1.        1.      |       |         |       |          |                                    |
| 61.                                    STORE TABLE FULL ACCESS | SYS_TEMP_0FD9D71E1_B445AE36 |       1.     2.         1.     + 5 |     1.        1.      |       |         |       |          |                                    |
| 62.                              USE OF JOIN FILTER | : BF0003 |    1884 |    88.         1.     + 5 |     1.        1.      |       |         |       |          |                                    |
| 63.                               STORE TABLE FULL ACCESS | TM_R_REP |    1884 |    88.         1.     + 5 |     1.        1.      |       |         |       |          |                                    |
| 64.                           USE OF JOIN FILTER | : BF0002 |    7449.    90.         1.     + 5 |     1.      444.      |       |         |       |          |                                    |
| 65.                            RANGE OF SINGLE PARTITION |                             |    7449.    90.         5.     + 1 |     1.      444.      |       |         |       |     0.65 | Cpu (1)                            |
| 66.                             STORE TABLE FULL ACCESS | PC_T_REP |    7449.    90.         1.     + 5 |     1.      444.      |       |         |       |          |                                    |
| 67.                          VIEW                                |                             |     105.     2.         1.     + 5 |     1.    13637 |      |       |         |       |          |                                    |
| 68.                           STORE TABLE FULL ACCESS | SYS_TEMP_0FD9D71E0_B445AE36 |     105.     2.         1.     + 5 |     1.    13637 |      |       |         |       |          |                                    |
| 69.                         STORE TABLE FULL ACCESS | TM_REP                      |    7136 |     7.         1.     + 5 |     1.     7137 |      |       |         |       |          |                                    |
| 70.                        STORE TABLE FULL ACCESS | L_OP                        |   19382 | 12813 |        77.     + 5 |     1.    43879 | 565. 551 MB | 98.18% |   15 M |          |                                    |
| 71.                       TABLE ACCESS BY INDEX ROWID | L_US                        |       1.     1.        79.     + 3 |   15 M |      15 M |   26. 208KO |         |       |    19.61 | Cpu (30)                           |
| 72.                        INDEX UNIQUE SCAN | L_US_PK                     |       1.       |        77.     + 5 |   15 M |      15 M |    2. 16384.         |       |     9 h 15 | Cpu (14)                           |
| 73.                     INDEX UNIQUE SCAN | L_A_PK                      |       1.     1.       151.     + 2 | 8238 |     8238 | 3269 | 26 MB |         |       |     2.61 | Cpu (1)                            |
|    |                                                              |                             |         |       |           |        |       |          |      |       |         |       |          | monobloc cell physical read (3) |
| 74.                    STORE TABLE FULL ACCESS | OPP_C_DIM |    2304 |     4.         1.    + 81 |     1.     2304 |    3. 112 KB |         |       |          |                                    |
| 75.                KIND OF BUFFER.                             |    7449. 13107 |         1.    + 81 |     1.     7449.      |       |         | 370K |          |                                    |
| 76.                 RANGE OF SINGLE PARTITION |                             |    7449.    90.         1.    + 81 |     1.     7449.      |       |         |       |          |                                    |
| 77.                  STORE TABLE FULL ACCESS | PC_T_REP |    7449.    90.         1.    + 81 |     1.     7449.      |       |         |       |          |                                    |
| 78.               STORE TABLE FULL ACCESS | TM_R_REP |    1884 |    88.         1.    + 81 |     1.     1929 |      |       |         |       |          |                                    |
| 79.             VIEW                                             |                             |       1.     2.         1.    + 81 |     1.        1.      |       |         |       |          |                                    |
| 80.              USE OF JOIN FILTER | : BF0000 |       1.     2.         1.    + 81 |     1.        1.      |       |         |       |          |                                    |
| 81.               STORE TABLE FULL ACCESS | SYS_TEMP_0FD9D71E1_B445AE36 |       1.     2.         1.    + 81 |     1.        1.      |       |         |       |          |                                    |
| 82.            VIEW                                              |                             |     105.     2.         1.    + 81 |     1.    13637 |      |       |         |       |          |                                    |
| 83.             STORE TABLE FULL ACCESS | SYS_TEMP_0FD9D71E0_B445AE36 |     105.     2.         1.    + 81 |     1.    13637 |      |       |         |       |          |                                    |
| 84.           STORE TABLE FULL ACCESS | TM_REP                      |    7136 |     7.         1.    + 81 |     1.     7137 |      |       |         |       |          |                                    |
| 85.          STORE TABLE FULL ACCESS | TM_REP                      |    7136 |     7.         1.    + 81 |     1.     7137 |      |       |         |       |          |                                    |
| 86.         STORE TABLE FULL ACCESS | L_OP                        |   19382 | 12813 |        72.    + 81 |     1.    43879 | 593. 577 MB | 98,44% |   15 M |          |                                    |
| 87.        TABLE ACCESS BY INDEX ROWID | L_US                        |       1.     1.        72.    + 81 |   15 M |      15 M |      |       |         |       |    13.73. Cpu (21)                           |
| 88.         INDEX UNIQUE SCAN | L_US_PK                     |       1.       |        73.    + 80 |   15 M |      15 M |      |       |         |       |     9.80 | Cpu (15)                           |
| 89.      STORE TABLE FULL ACCESS | OPP_C_DIM |    2304 |     4.         1.   152.     1.     2304 |      |       |         |       |          |                                    |
===============================================================================================================================================================================================================================================
Information of predicates (identified by the operation identity card):
---------------------------------------------------
2. (("MEMBER_KEY_SYM" =: B1 ET "IS_LEAF" = 1) filter)
8 - storage("T7171".") CHILD_REP_ID "= 939)
filter ("T7171". ("CHILD_REP_ID" = 939)
10 - storage("T7167".") ANCESTOR_KEY "= 939)
filter ("T7167". ("ANCESTOR_KEY" = 939)
13 - access("T7167".") SALESYEARMONTH "= 'T7171'." SALES_YEAR_MONTH' AND 'T7167 '. "ANCESTOR_KEY"= "T7171". ("' CHILD_REP_ID")
filter (CASE WHEN TO_CHAR ("T7171". "CHILD_REP_ID_N") AS 9999% ' THEN 'ALL UNASSIGNED' | " CAST ("T7167". ("TERRITORY_ID" AS A VARCHAR (20)) ELSE 'T6715 '. "" NAME "| "
'||" T6715 ". "" MIDDLE_NAME "| " '||" T6715 ". ("" LAST_NAME "END ="JOES CRAMER")
15 - access("T7171".") CHILD_REP_ID_N "= 'T6715'." REP_ID")
16 - access("T7171".") CH_ID_SYM '= 'D1'.' C1")
20 - storage("T7171".") CHILD_REP_ID "= 939)
filter ("T7171". ("CHILD_REP_ID" = 939)
22 - storage("T7167".") ANCESTOR_KEY "= 939)
filter ("T7167". ("ANCESTOR_KEY" = 939)
23 - storage("T7171".") SALES_YEAR_MONTH "= 201505)
filter ("T7171". ("SALES_YEAR_MONTH" = 201505)
26 - storage("T7167".") SALESYEARMONTH "= 201505)
filter ("T7167". ("SALESYEARMONTH" = 201505)
28 - access (TO_CHAR (INTERNAL_FUNCTION ("L_OP". "CLOSEDATE"), "YYYYMM") = TO_CHAR ("OPP_C_DIM". " PERIOD") AND
TO_CHAR ("OPP_C_DIM". "OFFER_CODE") = "L_OP". ("' OFFER_CODE__C")
29 - filter("TM_REP".") REP_NUM "=" 0"|" » « « « L_US «. » REP_EMPLOYEE_NUMBER__C')
31 - access("T7315".") YEAR_MONTH «= TO_NUMBER (TO_CHAR (INTERNAL_FUNCTION ("L_OP".» CLOSEDATE"),"YYYYMM")) AND
'T7167 '. «SALESYEARMONTH «= TO_NUMBER (TO_CHAR (INTERNAL_FUNCTION ("L_OP".» (((("" CLOSEDATE "),"YYYYMM")))
32 - access("T7171".") CHILD_REP_ID_N "= 'T6715'." REP_ID")
33 - access("T7167".") MEMBER_KEY "=" TM_REP. " ("" REP_ID ")
34 - access("T7171".") CH_ID_SYM '= 'D1'.' C1")
35 - access("T7171".") CH_ID_SYM '= 'D1'.' C1")
37 - access (SYS_OP_MAP_NONNULL ("D2". "C16") = SYS_OP_MAP_NONNULL ("T7171". " CH_ID_SYM") AND"T7167 ". "SALESYEARMONTH"= "T7171". "" SALES_YEAR_MONTH "AND
'T7167 '. "ANCESTOR_KEY"= "T7171". ("' CHILD_REP_ID")
39 - access (SYS_OP_MAP_NONNULL ("D2". "C15") = SYS_OP_MAP_NONNULL ("T7315". " MONTH_NUMERIC'))
40 - storage("T7315".") YEAR_MONTH "= 201505)
filter ("T7315". ("YEAR_MONTH" = 201505)
43 - access (TO_CHAR (INTERNAL_FUNCTION ("L_OP". "CLOSEDATE"), "YYYYMM") = TO_CHAR ("OPP_C_DIM". " PERIOD") AND
TO_CHAR ("OPP_C_DIM". "OFFER_CODE") = "L_OP". ("' OFFER_CODE__C")
45 - filter("TM_REP".") REP_NUM "=" 0"|" » « « « L_US «. » REP_EMPLOYEE_NUMBER__C')
47 - access("T7315".") YEAR_MONTH «= TO_NUMBER (TO_CHAR (INTERNAL_FUNCTION ("L_OP".» CLOSEDATE"),"YYYYMM")) AND
'T7167 '. «SALESYEARMONTH «= TO_NUMBER (TO_CHAR (INTERNAL_FUNCTION ("L_OP".» (((("" CLOSEDATE "),"YYYYMM")))
48 - access("T7167".") MEMBER_KEY "=" TM_REP. " ("" REP_ID ")
49 - access("T7171".") CH_ID_SYM '= 'D1'.' C1")
50 - access("T7167".") SALESYEARMONTH "= 'T7171'." SALES_YEAR_MONTH' AND 'T7167 '. "ANCESTOR_KEY"= "T7171". ("' CHILD_REP_ID")
53 - access("T7171".") CH_ID_SYM "=" C1")
56 - storage("T7315".") YEAR_MONTH "= 201505)
filter ("T7315". ("YEAR_MONTH" = 201505)
63 - storage (("T7171". "SALES_YEAR_MONTH" = 201505 AND SYS_OP_BLOOM_FILTER (: BF0000, "T7171" ".") CH_ID_SYM')))
filter (("T7171". "SALES_YEAR_MONTH" = 201505 AND SYS_OP_BLOOM_FILTER (: BF0000, "T7171" ".") CH_ID_SYM')))
66 - storage (("T7167". "SALESYEARMONTH" = 201505 AND SYS_OP_BLOOM_FILTER (: BF0000, "T7167" ".") SALESYEARMONTH', 'T7167 '. ((("" ANCESTOR_KEY ")))
filter (("T7167". "SALESYEARMONTH" = 201505 AND SYS_OP_BLOOM_FILTER (: BF0000, "T7167" ".") SALESYEARMONTH', 'T7167 '. ((("" ANCESTOR_KEY ")))
70 - storage ((TO_NUMBER (TO_CHAR (INTERNAL_FUNCTION ("L_OP". "CLOSEDATE"), "YYYYMM")) > = 201505 AND "
TO_NUMBER (TO_CHAR (INTERNAL_FUNCTION ("L_OP". "CLOSEDATE"), "YYYYMM")) (< = 201505)) "
filter ((TO_NUMBER (TO_CHAR (INTERNAL_FUNCTION ("L_OP". "CLOSEDATE"), "YYYYMM")) > = 201505 AND "
TO_NUMBER (TO_CHAR (INTERNAL_FUNCTION ("L_OP". "CLOSEDATE"), "YYYYMM")) (< = 201505)) "
72 - access("L_OP".") OWNERID "=" L_US. " (' ' ID ')
73 - access("T765190".") WITH THE ID "=" L_OP. " ("' ACCOUNTID ')
77 - storage("T7167".") SALESYEARMONTH "= 201505)
filter ("T7167". ("SALESYEARMONTH" = 201505)
78 - storage("T7171".") SALES_YEAR_MONTH "= 201505)
filter ("T7171". ("SALES_YEAR_MONTH" = 201505)
81 - storage (SYS_OP_BLOOM_FILTER (: BF0000, "C0"))
filter (SYS_OP_BLOOM_FILTER (: BF0000, "C0"))
86 - storage ((TO_NUMBER (TO_CHAR (INTERNAL_FUNCTION ("L_OP". "CLOSEDATE"), "YYYYMM")) > = 201505 AND "
TO_NUMBER (TO_CHAR (INTERNAL_FUNCTION ("L_OP". "CLOSEDATE"), "YYYYMM")) (< = 201505)) "
filter ((TO_NUMBER (TO_CHAR (INTERNAL_FUNCTION ("L_OP". "CLOSEDATE"), "YYYYMM")) > = 201505 AND "
TO_NUMBER (TO_CHAR (INTERNAL_FUNCTION ("L_OP". "CLOSEDATE"), "YYYYMM")) (< = 201505)) "
88 - access("L_OP".") OWNERID "=" L_US. " (' ' ID ')

Note
-----
-dynamic sample used for this survey (level = 4)
-Automatic DOP: calculated degree of parallelism is 1 because of the parallel threshold

Although the table meet statistical why dynamic sampling is to be used? Why 15 million times ID 71, 72, 87 and 88 are executed, curious because that is where most of the time is spent. How can we reduce this 15 million probes?
Suggestions to reduce the response time sql would be useful.
Post edited by: Yasu masking of sensitive information (literal value)

YASU says:

For educational purposes could you please clarify why the optimizer has evaluated the join condition in the functioning of the FILTER to 15 million lines?

This is unusual, but TM_REP is attached to another PC_T_REP table using a join operation, so maybe it's the explanation of why it is moved to a FILTER operation had been delayed - could also be a side effect of the combination of ANSI join processing (Oracle internally transforms ANSI joins in Oracle join syntax) and the transformation of outer join internally.

Very curious to know how this is possible, could you please give us the hint/tour, you can use to push the inner join down execution plan is evaluated as soon as possible to reduce the data to be processed? I have a sql plus, where the situation is almost similar - ranks of filtering 2 million to the hash JOIN operation and return 0 rows. I can post the details of sql here but not to mix different sql question in the same post. Please let me know if you would like to give the details of this sql in this same thread, or a different thread? I searched for this type of information, but to no avail, so could you please suggest how this is possible, if not for this long sql then at least please provide a few examples/suggestions?

Normally you can influence this through the appropriate join order, for example with the help of the LEADING indicator, for filter indicator PUSH_SUBQ subqueries can also be useful for filtering at the beginning. But here the comment of Franck is particularly important - by leaning on the Cartesian join this problem here should be less relevant.

As I already said I would recommend here from scratch and think that all that this query is supposed to average and the question why most outer joins is actually converted into inner joins - the current query example returns the correct result?

Randolf

Get the response time more with First_Rows Hint.
Hello
I use 10.2.0.1.0 oracle version. I have a sql query that gives performance with cutting-edge FIRST_ROWS problem. I expect the best response time with suspicion of "FIRST_ROWS (5)", but his is the worst, with use of a different set of the index, which is local to the partition. Please, help me to understand, the reason behind this change in negative execution path?
```
     First query gives all the ~3488 rows within ~1 minutes but the query with HINT is taking ~15 minutes for providing initial few rows itself. 
For second one i am not able to get the exact and estimated cardinality stats , as it was taking lot of time for completion, so providing Autotrace plan only.
     
Main Query:
```
Published by: 930254 on October 15, 2012 04:55
930254 wrote:
Yes, Jonathan, in fact in the first case, i 'I' table is being analyzed using an overall index, but suspicion FIRST_ROW sound using the index that is local to the partition. resulting in the digitization of all partitions of 448. I think it's causing bottleneck. Is there something like: FIRST_ROW suspicion that affect this type of systematic index scan?

In the first case the optimizer has unnested subquery of REACTION and used to bring to the table, I, and that's what dictated the choice of index.

In the case of first_rows (5) decided that the range index scan will take adequate data if some time he chose a different index - running subqueries in the REACTION as a subquery for filter on each line. But it is the estimate of how long it will find adequate data (and how much time he will have to run the subquery to eliminate unnecessary data) does not.

Concerning
Jonathan Lewis

Response time
One of my customer/user access to our database is having a problem with respect to the response time of the database. The response time is very slow, this problem occurred recently, but before the answer time is about 2 to 3 minutes but now a query will consume almost 1 hour before the database to react. The request includes this statement VIEW_ACCOUNT_PAYM_STATUS.

Hope you can help me with this.

Thank you
Hello
Are all applications started slow response or a single applicaiotn/report?
What version of oracle you are using. You should try to trace the user's session when it starts executing the statement. If you're on 10g, you can use the followins as the user SYS command to start tracing, and it will show you events in files of follow-up to find out where your query is spend more time waiting.
```
SQL> EXEC DBMS_MONITOR.session_trace_enable(session_id =>1602, serial_num=>1091, waits=>TRUE, binds=>FALSE);
```
Salman

Satellite M100-165 - for the LCD Panel response time

Hello.

Anyone know where I can find information on the reaction time of my LCD screen on my M100-165?

Does anyone know what is the response time LCD m100-165 (or m100 series)?

Thx for replies :)

Hello

The M100 series was delivered with a display type 200 WXGA 14.1 LTN141W1-L03-0.
To my knowledge this display should support a response speed of 25ms.

Get the response time data VI

Hi guys,.

I am trying to use CD get time response data VI my VI. When I choose the pair of input-output, I can get the response data determined by the digital input to the output value. However, I need more of a pair of response data. I try to use the list of input-output, but there is no output data and response time of the VI with table 1 d of numbers.

My question is how to use the CD get time VI data response with the list of inputs-outputs configuration? Thank you.

Hey, Shapiro,.

I think the problem is you have two 0 items in the above table for you will be out this definition data twice. Let me know if this does not solve the problem for you.

Response time of PCI-6602

Dear users of the forum,

I use a Counter/Timer OR PCI - 6602 for send TTL signals to another device in our laboratory. I send the signal every ~ 1-5 ms, but this time is not fixed (it depends on some other process that I do in my program of LabVIEW), so I can't use a continuous waveform.

So, I wrote a short test program to familiarize yourself with the PCI-6602 (see attachment).

If I send a pulse, it seems I can do this just about every 14 ms (at least this is calculated with the tick counts lag which is not very accurate; but to count the pulses with a meter gives almost as much time). So, it seems that the PCI-6602 has too long a response time for my application!

Can someone tell me if he made the same comment? Either I use the bad vi/treat the PCI-6602 in the bad sense? If Yes, what should I do to make my small test program and finally my main program faster?

I would be recognizing all the help and the comment!

partial81,

I have another idea for you to try. Starting the 6602 being the operation that takes the most time I wrote an example which uses a trigger to start to generate the impulse and puts in place the meter to retriggered. Basically whenever you issue a start trigger, the meter will generate a pulse. I then use a digital line on the 6602 to generate this trigger to start (I use PFI0 and Port0/$line0 which is actually the same line in the material). For the reenclenchee generation, wait until what is not useful, so I replaced it with a 1 ms wait.

Can you try this and see if it works better for you?

Dan

DAC single sample write response time

I use the acquisition of data USB-6259. I wrote a simple loop to write permanently a single sample of an output to check the next time of turing analog voltage pos & neg. I have the 'writing analog DBL 1Chan 1Samp' connected to a 'multiply by neg 1 "in a loop. I run the application, and it seems that the response time is about 3msec between +/-. It's far too slow for my application. My application requires constantly reading and setting of the tensions. I get a high sampling frequency if I'm out a waveform. However, I didn't go out a waveform. I went out a voltage in response to a voltage reading. Is it possible to have a shorter response time? Is there another method (using C?) to improve response times?

Erik,

Windows is deterministic up to 1 ms, so there is no way we could get this application in the field of speed you need with the current hardware. I think that you could implement this with an FPGA, and we have many options available.

Incredibly slow Internet response time.

Original title: taskbar

I had a problem with incredibly response times Internet. After reboot, I discovered in the taskbar, the icon of the single computer that deals with network connections, i.e. wifi had an x in it, which means it is turned off. (This isn't the icon to connect to the LAN of double work). Because my PC is using wifi and is not also connected to the cable, I was wondering what task is connected to wifi.

I also noticed that my Internet speed of response actually works at an acceptable speed now that the icon shows it is off. Which task is this icon, so that I can disable it using msconfig and task is WiFi so that one is not?

I use a Dell desktop computer, through Time Warner Cable. I had the SP3 for some time and that you have not added any new programs or updates, that I remember for a while.

The only change in my computer added wifi (after moving to a new House/State) about six months ago.

As a further complication, when I logged on today, connecting to the wifi network shown in the taskbar opened and ran into a mode of connection 'very good '. So yesterday and the previous week, I had access to the Internet with it NOT connected. My taskbar displays a computer screen green with waves in the upper left corner and says "Netgear WNA3100 is connected to...". "my camera wifi router in the basement next to the TW modem.

Correct me if I'm wrong, but I think that there are two connections wifi different trying to run... one that was working yesterday and one today showing tasks in my bar.

I blame that for my calculation of the slow speeds.

Looks like you have three icons of network connection...

1. area (cable) connection icon - two screens - probably with a red X

2. the icon of Windows wireless - a blue screen with 'waves '.

3 - Netgear wireless connection icon describe you it as 'green with waves screen '.

It also seems that maybe you think that 2 and 3 are separate connections. This is not the case, they will just separate indicators of the same wireless connection.

Reading between the lines a bit, my guess is that you used to have only 1 and 2, but now you have the 3rd too. If I'm right, probably, what happened is that you have started the application of Netgear wireless configuration, which experience tells me tends to 'support' of Windows wireless configuration without even asking if you want that to happen. All you need to do to get rid of this icon of the green screen is open the Netgear configuration (via its system tray icon) and find a check box saying "let Windows to manage my wireless network connection" (or words to that effect, in addition, it is that the word 'zero' in the text). If you have no network connection after doing this, then you were always in a Netgear configuration and you will have two choices...
1. Start the Netgear form the menu start and reverse the changes that you just made
2. Configure Windows to control the wireless connection
If you want to Setup Netgear instead of Windows use, I think that you will have to put up with the two icons.

Tricky

Pavilion 17-F001dx: 'Windows 8 using 100% of the HARD drives with high average response time and low write speed '.

It turns out that it is a pretty known issue windows 8.1 users infestation since at least 2013 and there is not a simple fix, then it cannot be * completely * lack of hp. but I've had two of these laptops, both the same model, one needing to be returned and exchanged for a problem absolutely no report with (hardware failure: ethernet port does not work with lights taped). Both are renovated. Both have been extreemly slow and unresponsive even compared to the lower Brazos powered by the laptop that I had before, but I recently decided to investigate why.

So if there is something specific HP going on here, I hope that there is a simple fix. My average response time went upward as well more than a minute (> 60, 000ms), so that I'm an aberrant case here against this problem of reactivity/band bandwidth hardrive typical windows 8.1.

Edit: there is a case with another HP pavilion laptop (intel powered, so there may be a problem of storage driver intel described in the first link) being much worse.

Did not want to resort to that, but,.
Going to a new facility to clean up an image of Windows Pro 8.1 from DreamSpark for my school.

Disappointed by the lack of response. Given the odd subdomain name (h30434), I'm wondering if this forum has been abandoned.

WebMonitor strong expression of mailBody response time

Hello

Please, help me to create expression for WebMonitor strong expression of response time mailBody.

I got the expression for the availability of transaction webMonitor, I've pasted below.

could someone please help me create a same response time?

def message = "Page is not available. Cannot access the URL "+ scope.get("measuredObject/url") +". ";" "
def httpStatus = null;
def values = $scope #httpStatus # .values (scope);
{if (values)}
httpStatus = values.last ()?. GetValue;
}
If {(httpStatus)
def httpStatusMessage = getWebMonitorHttpStatusMessage(httpStatus?.) (ToString());
message = message & "HTTP status is ${httpStatus} - {httpStatusMessage}.";
}
message += "Please contact technical support.";
return the message;

Hi Vicky,

Just try to understand what is missing from the message into the existing rule.

WebMonitor Transaction Response Time Check rule

has a variable of severity level of alarmMsg that references 2 other variables are variables rule.

-alarmMsgPrefix rule variable named transaction - "high response time. "The response time of ${scope.measuredObject.name} of the transaction exceeds.

-variable rule alarmMsgSuffix retrieves the response time

def data = $scope #responseTime # .values (scope);
responseTime def = 0;
{if (Data)}
responseTime = data [0] .getValue (.avg)? : 0 ;
return "ms, current response time is" responseTime + "ms".
}

Golan

Response time of the provider for BlackBerry World Portal

Is it just me or response time to requests for change appear to have increased? I usually get 1 to 2 days for an update of the app and 1 day for app list changes.

During the last two weeks, I've waited a week for an update of the app. Even more, I've been waiting 3 days for the list of updates (images, text) so that registration corresponds to the app update.

The funny thing is, I submit the updated list of the next day to submit the app. They got approved within 1 to 2 days. I deleted them after waiting for 5 days and no updates to the app.

Any ideas?

We always have to approve new and updated applications updated in 2 to 5 business days, and that has not changed. Monday was a day public holiday here in the Canada, what would elimate that as a working day for this week. The team strives to make upward and toward the more usual period of 2 days.

Analysis of response time of NAM

I have 2 small question:

First: How Cisco NAM can calculate server, client and network responses while it is not the initiator of the traffic? It is based on the timestamps in data packets? All protocols put a timestamp in the header?

The second question is: how NAM classify clients and servers? as I see the servers appear as a customer.

Thanks in advance.

Performance (IAP) intelligent application monitoring is a key feature that provides the Nam: an ability to measure the response time of the transactions between the client and the server.

NAM monitors the flow of TCP packets between the client and the server and data response time to bring more visibility in time of response measures (ART) and the latency of the network.

Next image will share more details:

NAM request time response (it shows a representation of the total time of the operation as opposed to application response time)

Transaction time / response time measurements (lists and describes measures ART measured by NAM)

Possible NAM monitors conversation and the TCP packet flow between applications/server customers and where it grows the clients and servers.

-Thank you

Vinod

To encourage contributors. RATE besoin.*

Response time of Structure event &amp; simultaneous execution of events

Similar Questions

Maybe you are looking for

Response time of Structure event & simultaneous execution of events