Skip to Content
avatar image
Former Member

SM50: Direct Read & Sequential Read over 4500000

Hello everybody,

I do not know what SM50 exactly shows. But we got really performance problems.

After sending approximatly 1500 IDOCs today we can see in SM50

Direct Read 1.850.295

Sequential Read 3.502.006

What does this mean? Could this be the indicator that something should be optimized? Whart should be optimized in this special case?

Regards Mario

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Dec 06, 2006 at 04:07 PM
    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Mario, you got more result using other way for the analisys on the performances:

      SXMB_MONI --> Select the message --> Response --> PerformanceHeader

      In this way you will have the possility to check in which fase XI is slow.

      It may appear a little bit complicated at the beginnig but it is the only way to know exaclty what happens in the XI pipeline.

      Here an example, in bold the timestamp of the differente phases

      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

      - <!-- Response

      -->

      - http://sap.com/xi/XI/Message/30">

      - <SAP:RunTimeItem>

      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>

      <SAP:Timestamp type="begin" host="sapxixxx"><b>20061206092235.643823</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>

      <SAP:Timestamp type="end" host="sapxixxx"><b>20061206092438.380442</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>

      <SAP:Timestamp type="begin" host="sapxixxx"><b>20061206092438.380466</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>

      <SAP:Timestamp type="end" host="sapxixxx"><b>20061206092438.503226</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>

      <SAP:Timestamp type="begin" host="sapxixxx"><b>20061206092438.504437</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>

      <SAP:Timestamp type="end" host="sapxixxx"><b>20061206092438.515319</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>

      <SAP:Timestamp type="begin" host="sapxixxx"><b>20061206092438.542918</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>

      <SAP:Timestamp type="end" host="sapxixxx"><b>20061206092438.548712</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>

      <SAP:Timestamp type="begin" host="sapxixxx"><b>20061206092438.574059</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>

      <SAP:Timestamp type="end" host="sapxixxx"><b>20061206092438.579975</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>

      <SAP:Timestamp type="begin" host="sapxixxx"><b>20061206092438.579992</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>

      <SAP:Timestamp type="end" host="sapxixxx"><b>20061206092438.734069</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>

      <SAP:Timestamp type="begin" host="sapxixxx"><b>20061206092438.735363</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>

      <SAP:Timestamp type="end" host="sapxixxx"><b>20061206092438.931395</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>

      <SAP:Timestamp type="begin" host="sapxixxx"><b>20061206092438.947041</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>

      <SAP:Timestamp type="end" host="sapxixxx"><b>20061206092438.970678</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>

      <SAP:Timestamp type="begin" host="sapxixxx"><b>20061206092438.989097</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      - <SAP:RunTimeItem>

      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>

      <SAP:Timestamp type="end" host="sapxixxx"><b>20061206092439.051537</b></SAP:Timestamp>

      </SAP:RunTimeItem>

      </SAP:PerformanceHeader>

      Regards,

      Sandro

  • avatar image
    Former Member
    Dec 06, 2006 at 04:24 PM

    Mario,

    The workprocess overview is the central transaction to get an overview over the current processes running in the Integration Engine. The process overview is only a snapshot analysis. Thus, you have to refresh the data several times to get a feeling for the dynamics of the processes. The most important questions to be asked are as follows:

    a)How many work processes are being used on average?

    b)Which user is using these processes? The Business Process Engine (ccBPM) will show up with user WF-BATCH, whereas the pipeline execution is typically executed by XIAFUSER. The latter user, however, is not a fixed user, but the last one that activated the inbound scheduler (see SAP Note 369007, question 8).

    c) Are there any long running processes and if so, what are these processes doing with regard to used reports and accessed tables?

    d) As a rule of thumb for the initial configuration, the number of DIA work process should be around four times the number of CPU in your XI system (rdisp/wp_no_dia = 4 * #CPU).

    For further help refer :

    http://help.sap.com/saphelp_erp2004/helpdata/EN/69/c24e104ba111d189750000e8322d00/content.htm

    http://help.sap.com/saphelp_nw2004s/helpdata/en/7a/6b1538e665c93ee10000009b38f842/content.htm

    Hope this helps......

    ---Satish

    Add comment
    10|10000 characters needed characters exceeded