Relation between RFC time and Roll wait time

[peter_strauss]

Hello

What is the relation between RFC time and Roll wait time?

In a diagram from E2E100 training I took recently the relationship is made out to be:

RFC+CPIC = some processing time + Roll wait time

Something like this

Processing----

Roll wait-------

Roll in

................

RFC+CPIC----

In the diagram I saw it shows that roll out occurs during processing.

Assumming that the user context rolls out and then rolls in again, wouldn't "Wait" time occur when the request comes back and the dispatcher has to assign the request to a work process?

Is this wait time calculated as "Wait" time or is it calculated as "Roll wait" time?

I was forced to think about this because of a STAD record I have with high Roll wait time, but with low RFC time as well as zero GUI time. If "Wait" time when the request comes back from RFC is included in "Roll wait" then it might explain what i'm seeing.

Kind regards,

Peter

[peter_strauss]

"Roll wait time" is defined as the time an SAP work process has to wait for a response from an RFC. In other words, it is the time dedicated by the R/3 system to waiting for the return value of an RFC call plus the CPIC time required to create the connection for that RFC to an outside system. In 4.6x releases, this often includes time to process on the end user's PC as well when the executed transaction requires an RFC to transfer data from the application server to SAP GUI.

Higher roll wait times for 4.6x are common because of the dependency on local GUI controls and major increases in the use of RFCs for communication from R/3 to the end user PC.

http://help.sap.com/saphelp_nw04s/helpdata/en/21/2c8f38c7215428e10000009b38f8cf/content.htm

[Former Member]

"Roll wait time" is defined as the time an SAP work process has to wait for a response from an RFC. In other words, it is the time dedicated by the R/3 system to waiting for the return value of an RFC call plus the CPIC time required to create the connection for that RFC to an outside system. In 4.6x releases, this often includes time to process on the end user's PC as well when the executed transaction requires an RFC to transfer data from the application server to SAP GUI.

Higher roll wait times for 4.6x are common because of the dependency on local GUI controls and major increases in the use of RFCs for communication from R/3 to the end user PC.

http://help.sap.com/saphelp_nw04s/helpdata/en/21/2c8f38c7215428e10000009b38f8cf/content.htm

[peter_strauss]

Hello Santosh,

Thank you for your reply.

I would like to know how time spend in the dispatcher by a request coming back from an RFC is calculated.

When the RFC is made the user context is rolled out of the work process so the work process becomes free. When the RFC comes back it has to be assigned to a new work process. This means that a bit of time would need to be spent in the dispatcher. Would this time be measured as "wait" time or is it part of "Roll wait time?

From the definition you gave of "Roll wait time", "it is the time dedicated by the R/3 system to waiting for the return value of an RFC call plus the CPIC time required to create the connection for that RFC to an outside system", one would think that the time spent in the dispatcher by a returning RFC would be measured as "wait time" the same as when the dialog request first comes in from the front end. I've never seen a diagram that explained this satisfactorily.

Kind regards,

Peter

[peter_strauss]

Not really answered but I'll put it away because I don't want to see it in my unanswered box any more.