CPIC/RFC Time vs Total Response time

Hi experts,
We are experiencing performance issues in our SRM system, when checking the transaction ST03 we have identified a high dialog comsuption time in the Average RFC Interface time (CPIC/RFC), this time is even higher than the Total Average Reponse Time per dialog step.
Could you please let us know if the component Average RFC Interface time (CPIC/RFC) is part of the average response time? We can't understand why this time is almos the double than the
Thanks and best regards,

Hello Sowmya,
I would normally suggest a solution without having detailed background about your system such as SAP kernel, SAP release etc.
But the following SAP Note almost describes your issue.
2071875 - Incorrect Average RFC Interface Time ("CPIC/RFC") in ST03N Workload Overview ("Average time per step in ms")
Hope that helps.
Regards,
Siddhesh

Similar Messages

Session manager is taking 10% of the total response time

Hi
As per our recent analyses session manager is taking around
10% of the total response time, we have done the archiving of data
however it still taking around 9% of the total response time, I have checked few notes from service market place. However i would request you to suggest something
sap notes
164102
203617
161053
26417
203924
My system configuration
SAP System ID WCP
SAP Component ECC 5.0
SAP Release ERP 2004
Database System Oracle 10.2.0.4
Operating System Windows Server 2003 on x86_32, AIX 5.3,
Windows Server 2003 on x86_64
Thanks in advance
Regards
Rizvi
+919874428887

Hi,
first check the user nodes from PROFGEN_CORR_REPORT_5 (from SE38)
Here you can find the user nodes for all users, and disable user nodes if any user had high utilization.
Please check SAP Note 203617
Regards
Nick Loy

High GUI Time - Causing high Response time

Hi All,
Average GUI Response time is approx 400 ms in my ECC 6.0 system, OS - HP UX, Database - Oracle 10.2.0.5.
I expect it should always be approx 200 ms, but as it is high it is contibuting to high overall response time.
I expect there are normally two ways of high GUI time :
1) High network time between Presentation layer( User System) and Application Layer(SAP Server).
2) High amount of time in Loading User Screen
For Option 2 I have checked we are using SAP access menu so there should not any problem with loading of User Access Menu.
Average Response time for session_manager is 2 Secs.
Please suggest me what all other ways available to improve GUI time,
Can there be other reasons of high GUI time and how can we make sure that high GUI time is only because of high Network time.
Please suggest.
Shivam

I believe in case you have multiple roundtrips per step, then the client performance comes into play as well. So if you have slow clients this could be an issue too.
Basically you are already looking in the right place (network connection), but i recommend you also check:
- roundtrips per step and amount of data sent to the client
- are all transactions having high gui times, or only a few?
- how is the situation on the clients?
- if you have clients working on prod and qas check the values on the qas system too
Cheers Michael

Incorrect Alerts CPU Time and Average Response Time

BUG
My Alert on Web app is consistently behaving incorrectly.
If I set an alert to monitor CPU Time at threshold 1.5 seconds, it's actually set to 1.5 milliseconds even though the graph shows a dotted red line at 1.5 seconds. The alert will trigger at 1.5 milliseconds threshold. So, instead, I have to set threshold
to 1500 seconds - the graph is completely useless showing a red dotted line at ~24 mins but the alert does then go off when CPU time goes above 1500 ms (aka 1.5 seconds).
The original portal alert seems to be fine - this problem is on new portal only. Unaffected by browser type - all browsers do the same thing (Just has to be said before someone asks).
This seems to apply to all metrics using seconds (Average Response Time acts in the same way)

Hii...
Am sure you are much aware " Components Response Time spectrum"
########Analyzing Performance Problems#################
--High wait time: Insufficient number of free work processes
--High roll-wait time: Communication problem with GUI, external system,
or large amount of data requested
--High load and generation time: SAP buffers (Program, CUA or Screen)
too small
--High database request time: CPU/memory bottleneck on database server;
communication problem with database server, expensive SQL statements,
database locks, missing indexes, missing statistics or small database buffer(s)
--High CPU time: Expensive ABAP processing, for example, processing
large tables; inefficient programming
--Processing time more than twice CPU time: CPU bottlenecks
If time aloows look at
Note 0000008963 - Definition of SAP response time/processing time/CPU time
Rgds

Macbook Pro Boot time and general response time slow.

I'm running 10.9 Mavericks.
Yesterday as I was doing my every day activites I realized randomly my macbook pro began preforming extremely poorly.
My problems:
Boot time now takes 2-3 minutes.
Applications take 2-3 minutes to open.
Applications will say they're open sometimes but will not display.
Applications will take several tries to quit.
Applications, especially Safari, will randomly crash.
Everything is slower and takes a while to do, even opening a simple folder will take a minute.
The things I have tried:
I ran a Hardware test and the results showed it is not a hardware problem.
I have reset the SMC and PRAM and the problems still occur.
I have Verified and repaired the Disk/Permissions, however it seems to stop mid-way through (after about an hour).
I can't seem to figure out what's wrong with it. I can re-install the OS but with my internet it is estimated to take 8 hours.
Any suggestions?

Your disk may be failing. Do not attempt to resintall the OS until your disk is healthy.
Backup your data immediately:
Before proceeding you should make sure you have a current backup. If it has been getting slower over time your disk could be a failing slowly. SATA drives have two retry modes: short and long. They can continue operating as read errors are increasing. The long retry cycle is very long and can cause significant performance degradation. If it has started long retries then it is likely to get worse and eventually fail. SSDs also have a failure mode where the fail slowly.
Time Machine Basics: http://support.apple.com/kb/ht1427
Most commonly used backup methods:
https://discussions.apple.com/docs/DOC-3045
Methodology to protect your data. Backups vs. Archives. Long-term data protection:
https://discussions.apple.com/docs/DOC-6031
Make a Genius Bar reservation http://www.apple.com/retail/geniusbar/ .
or find an Apple Authorized Service Provider https://locate.apple.com/country
If it is a failing disk, consider an upgrade to a 1 TB, 7200 RPM disk. Check out a one terabyte HGST 7K1000 7200 rpm, SATA III drive from OWC or consider an SSD.

SAP GoLive : File System Response Times and Online Redologs design

Hello,
A SAP Going Live Verification session has just been performed on our SAP Production environnement.
SAP ECC6
Oracle 10.2.0.2
Solaris 10
As usual, we received database configuration instructions, but I'm a little bit skeptical about two of them :
1/
We have been told that our file system read response times "do not meet the standard requirements"
The following datafile has ben considered having a too high average read time per block.
File name -Blocks read - Avg. read time (ms) -Total read time per datafile (ms)
/oracle/PMA/sapdata5/sr3700_10/sr3700.data10 67534 23 1553282
I'm surprised that an average read time of 23ms is considered a high value. What are exactly those "standard requirements" ?
2/
We have been asked to increase the size of the online redo logs which are already quite large (54Mb).
Actually we have BW loading that generates "Chekpoint not comlete" message every night.
I've read in sap note 79341 that :
"The disadvantage of big redo log files is the lower checkpoint frequency and the longer time Oracle needs for an instance recovery."
Frankly, I have problems undertanding this sentence.
Frequent checkpoints means more redo log file switches, means more archive redo log files generated. right ?
But how is it that frequent chekpoints should decrease the time necessary for recovery ?
Thank you.
Any useful help would be appreciated.

Hello
>> I'm surprised that an average read time of 23ms is considered a high value. What are exactly those "standard requirements" ?
The recommended ("standard") values are published at the end of sapnote #322896.
23 ms seems really a little bit high to me - for example we have round about 4 to 6 ms on our productive system (with SAN storage).
>> Frequent checkpoints means more redo log file switches, means more archive redo log files generated. right?
Correct.
>> But how is it that frequent chekpoints should decrease the time necessary for recovery ?
A checkpoint is occured on every logswitch (of the online redologfiles). On a checkpoint event the following 3 things are happening in an oracle database:
Every dirty block in the buffer cache is written down to the datafiles
The latest SCN is written (updated) into the datafile header
The latest SCN is also written to the controlfiles
If your redologfiles are larger ... checkpoints are not happening so often and in this case the dirty buffers are not written down to the datafiles (in the case of no free space in the buffer cache is needed). So if your instance crashes you need to apply more redologs to the datafiles to be in a consistent state (roll forward). If you have smaller redologfiles more log switches are occured and so the SCNs in the data file headers (and the corresponding data) are closer to the newest SCN -> ergo the recovery is faster.
But this concept does not really fit the reality because of oracle implements some algorithm to reduce the workload for the DBWR in the case of a checkpoint.
There are also several parameters (depends on the oracle version) which control that a required recovery time is kept. (for example FAST_START_MTTR_TARGET)
Regards
Stefan

Report to calculate avg response time for a transaction using ST03.

Hi Abap Gurus ,
I want to develop a report which calculates the average response time(ST 03) for a transaction on hourly basis.
I have read many threads like in which users are posting which tables/FM to use to extract data such as dialog step and total response time .
I am sure many would have created a report like this , would appeciate if you can share pseudo code for same.Any help regarding the same is highly appreciated...
Cheers,
Karan

http://jakarta.apache.org/jmeter/

SLR - transaction response time for all appl. servers together

Hi,
we want to have in SLR response time for defined transaction. We have activated necessary steps for monitoring transactions, started CPH and we can see in SLR average response times.
We have several application servers and we want to have in SLR TOTAL response time for all appl. servers together.
Is it possible? What is necessary steps to do it?
Thanks for all hints.
Regards,
Roman

Hi Andreas,
Another way to approach this would be to use CCMS transaction monitoring by maintaining table ALTRAMONI (in the satellite system) as described here: http://help.sap.com/saphelp_nw70/helpdata/en/b3/468e3b093d4031e10000000a11402f/content.htm
In RZ20 you'll be able to see the last 24 hours of performance data in a 1-hour granularity, as well as the last 30 minutes in a higher granularity. Depending on your requirements you can then configure alerting so that you get an email when performance passes a certain threshold.
Jon

ACE 4710: Find out the response time of a real server

Hi to everyone,
I have a couple of ACE 4710 and I need to find out what is the response time of a real server.
Is there a way for this?
Thank you for any answer!
giorgio romano

Hi,
Kindly add the following line in your serverfarm configuration:
predictor response syn-to-synack
Suppose your serverfarm looks like this:
serverfarm host AAA_FARM
predictor response syn-to-synack
probe HTTP_PROBE
probe TCP9001_PROBE
rserver SC106
inservice
rserver SC107
inservice
rserver SC108
inservice
rserver SC109
inservice
rserver SC110
inservice
rserver SC111
inservice
rserver SC112
inservice
rserver SC113
inservice
rserver SC114
inservice
rserver SC120
inservice
rserver SC131
inservice
And then use the following command to see the average response time from your rserver as follows:
ACE1/prod# show serverfarm AAA_FARM detail
serverfarm     : AAA_FARM, type: HOST
total rservers : 11
active rservers: 11
description    : ServerFarm AAA
state          : ACTIVE
predictor      : RESPONSE
method            : syn-to-synack
samples           : 8
failaction     : -
back-inservice    : 0
partial-threshold : 0
num times failover       : 0
num times back inservice : 0
total conn-dropcount : 0
Probe(s) :
HTTP_PROBE, type = HTTP
TCP9001_PROBE, type = TCP
----------connections-----------
real                  weight state        current    total      failures
---+---------------------+------+------------+----------+----------+---------
rserver: SC106
x.x.x.x.:0        8      OPERATIONAL 2          1125       0
max-conns            : 4000000   , out-of-rotation count : 0
min-conns            : 4000000
conn-rate-limit      : -         , out-of-rotation count : -
bandwidth-rate-limit : -         , out-of-rotation count : -
retcode out-of-rotation count : -
load value           : 0
average response time (usecs) : 81   ----> thats what you might be looking for
From other day :
rserver: SC114
x.x.x.x:0        8      OPERATIONAL 70         10903      2
max-conns            : 4000000   , out-of-rotation count : 0
min-conns            : 4000000
conn-rate-limit      : -         , out-of-rotation count : -
bandwidth-rate-limit : -         , out-of-rotation count : -
retcode out-of-rotation count : -
load value           : 0
         average response time (usecs) : 1334                       ----> thats what you might be looking for
For Serverfarm BBB_FARM
serverfarm     : BBB_FARM, type: HOST
total rservers : 1
active rservers: 1
description    : ServerFarm BBB
state          : ACTIVE
predictor      : RESPONSE
method            : syn-to-synack
samples           : 8
failaction     : -
back-inservice    : 0
partial-threshold : 0
num times failover       : 1
num times back inservice : 1
total conn-dropcount : 0
Probe(s) :
----------connections-----------
real                  weight state        current    total      failures
---+---------------------+------+------------+----------+----------+---------
rserver: SC208
x.x.x.x:0        8      OPERATIONAL 0          0          0
max-conns            : 4000000   , out-of-rotation count : 0
min-conns            : 4000000
conn-rate-limit      : -         , out-of-rotation count : -
bandwidth-rate-limit : -         , out-of-rotation count : -
retcode out-of-rotation count : -
load value           : 0
         average response time (usecs) : 0   ----> thats what you might be looking for
Use more detials for response predictor:
http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA3_1_0/configuration/slb/guide/rsfarms.html#wp1068831
Configuring the Application Response Predictor
To instruct the ACE to select the server with the lowest average response time for the specified response-time measurement based on the current connection count and server weight (if configured), use the predictor response command in server farm host or redirect configuration mode. This predictor is considered adaptive because the ACE continuously provides feedback to the load-balancing algorithm based on the behavior of the real server.
To select the appropriate server, the ACE measures the absolute response time for each server in the server farm and averages the result over a specified number of samples (if configured). With the default weight connection option configured, the ACE also takes into account the server's average response time and current connection count. This calculation results in a connection distribution that is proportional to the average response time of the server.
The syntax of this command is as follows:
predictor response {app-req-to-resp | syn-to-close | syn-to-synack}[samples number]
The keywords and arguments are as follows:
•app-request-to-resp—Measures the response time from when the ACE sends an HTTP request to a server to the time that the ACE receives a response from the server for that request.
•syn-to-close—Measures the response time from when the ACE sends a TCP SYN to a server to the time that the ACE receives a CLOSE from the server.
•syn-to-synack—Measures the response time from when the ACE sends a TCP SYN to a server to the time that the ACE receives the SYN-ACK from the server.
•samples number—(Optional) Specifies the number of samples over which you want to average the results of the response time measurement. Enter an integer from 1 to 16 in powers of 2. Valid values are 1, 2, 4, 8, and 16. The default is 8.
For example, to configure the response predictor to load balance a request based on the response time from when the ACE sends an HTTP request to a server to when the ACE receives a response back from the server and average the results over four samples, enter:
host1/Admin(config)# serverfarm SFARM1
host1/Admin(config-sfarm-host)# predictor response app-req-to-resp
samples 4
To reset the predictor method to the default of round-robin, enter:
host1/Admin(config-sfarm-host)# no predictor
To configure an additional parameter to take into account the current connection count of the servers in a server farm, use the weight connection command in server farm host predictor configuration mode. By default, this command is enabled. The syntax of this command is as follows:
weight connection
For example, enter:
host1/Admin(config)# serverfarm SF1
host1/Admin(config-sfarm-host)# predictor response app-request-to-resp
samples 4
host1/Admin(config-sfarm-host-predictor)# weight connection
To remove the current connection count from the calculation of the average server response time, enter:
host1/Admin(config-sfarm-host-predictor)# no weight connection
You can use threshold milliseconds parameter which is optional Specifies the required minimum average response time for a server. If the server response time is greater than the specified threshold value, the ACE removes the server from the load-balancing decision process (takes the server out of service).
Enter an integer from 1 to 300000 milliseconds (5 minutes). The default is no threshold (servers are not taken out of service).
In case if you have measures the response time from when the ACE sends a TCP SYN to a server to the time that the ACE receives a CLOSE from the server use syn-to-close      (already discussed previously)
If you have to measures the response time from when the ACE sends a TCP SYN to a server to the time that the ACE receives the SYN-ACK from the server use syn-to-synack   (already discussed previously)
SAMPLES parameter is optional and specifies the number of samples that you want to average from the results of the response time measurement and response time is used to select the server with the lowest response time for the requested response-time measurement. If you do not specify a response-time measurement method, the ACE uses the HTTP app-req-to-response method.
Whenever a server's load reaches zero, by default, the ACE uses the autoadjust feature to assign a maximum load value of 16000 to that server to prevent it from being flooded with new incoming connections. The ACE periodically adjusts this load value based on feedback from the server's SNMP probe and other configured options.
Using the least-loaded predictor with the configured server weight and the current connection count option enabled, the ACE calculates the final load of a real server as follows:
final load = weighted load Ã— static weight Ã— current connection count
where:
â€¢weighted load is the load reported by the SNMP probe
â€¢static weight is the configured weight of the real server
â€¢current connection count is the total number of active connections to the real server
The ACE recalculates the final load whenever the connection count changes, provided that the (config-sfarm-host-predictor) weight connection command is configured. If the (config-sfarm-host-predictor) weight connection command is not configured, the ACE updates the final load when the next load update arrives from the SNMP probe.
If two servers have the same lowest load (either zero or nonzero), the ACE load balances the connections between the two servers in a round-robin manner.
HTH
Plz rate if u find it useful.
Sachin

Query Tuning - Response time Statistics collection

Our Application is Load tested for a period of 1 hour with peak load.
For this specific period of time, say thousands of queries gets executed in the database,
What we need is say for one particular query " select XYZ from ABC" within this span of 1 hour, we need statistics like
Number of times Executed
Average Response time
Maximum response time
minimum response time
90th percentile response time ( sorted in ascending order, 90th percentile guy)
All these statistics are possible if i can get all the response times for that particular query for that period of 1 hour....
I tried using sql trace and TKPROF but unable to get all these statistics...
Application uses connection pooling, so connections are taken as and when needed...
Any thoughts on this?
Appreciate your help.

I don't think v$sqlarea can help me out with the exact stats i needed, but certainly it has lot of other stats to take. B/w there is no dictionary view called v$sqlstats.
There are other applications which share the same database where i am trying to capture for my application, so flushing cache which currently has 30K rows is not feasible solution.
Any more thoughts on this?

"Time stamp, Response time and Completion time" in CRM_DNO_MONITOR

Hi,
We have configured Service desk functionality in Solution Manager 4.0.
In CRM_DNO_MONITOR we were able to see all the data except "Time stamp(0), Response time(00:00:00) and Completion time(00:00:00)" of Service desk message.
Kindly let us know, how to configure so that "Time stamp, Response time and Completion time" should be displayed in CRM_DNO_MONITOR.
Best regards,
Bhaskar

Hi,
Do u want this for SLA?
In the service desk you have to assign the date profile to the SLFN transaction type.
For this you can use the standard date profile SLFN_HEADER.
award point if it helps you.
regards,
mahantesh

Benchmark response times using BIA.

Hi all
I ran some queries using BIA and logged their processing times. Now, I want to compare these processing times with "benchmark response times using BIA" just to make sure that these queries are performing optimally. Could you pls provide pointers/links to the same.
Regards
Niranjana

Following are the steps we do in order to get the benchmark data.
Assume you have Indexed a cube in BIA.
Without BIA:
1. Goto transaction RSRT2-->Select the query and click "Execute + Debug"
2. Under section "BIA Server"-->Check "Donot user BIA Index"
3. Under section "Others"--> Check "Display statistics data" and "Do not user cache"
4. Execute....After query complete click on Back button to see the statistics
5. Sum up the "Duration column" and Subtotal by column "Event Text"
6. We are interested on the item "datamanager" - note down the value
With BIA:
7. Goto transaction RSRT2-->Select the same query and click "Execute + Debug"
8. Under section "BIA Server"-->DONOT Check "Donot user BIA Index"
9. Under section "Others"--> Check "Display statistics data" and "Do not use cache"
10. Execute....After query complete click on Back button to see the statistics
11. Sum up the "Duration column" and Subtotal by column "Event Text"
12. We are interested on the item "datamanager" - note down the value
13. Click on "Aggregation layer"-->You should note the on the "aggregation" column the cube name should be suffixed with "$X" ( which indicates it uses BIA)
14. Here "viewed at" is sum of other two front columns...
In the above way you can benchmark between non-BIA vs BIA query performance. if you see even with BIA the performance is slow...then it could be bcoz of OLAP time...lot of calculation in the frontend etc...
In general we see the performance of BIA is fantastic...except sometimes the numbers are not matching between BIA and non-BIA queries...where we need to rebuild the indexes.
Hope it helps
Gopi

Slow Response Time on iPhone 3G

On or about r4.0 coming out I started experiencing significant Response Time delays moving between key's on my iPhone and not sure why. I believe this to be a Processor issue... anybody else out there experiencing this issue.
Example:
Select Setting icon on Home Screen... reasonable response time of 1-sec
Select General icon tab... 3-4 sec delay in response
Select another tab on General screen... another 3-4 sec delay before new screen appears.
Hit Home button to close General window... 3-4 sec delay...
Select Messaging icon... goes to white screen and 3-4 sec delay before messaging dialogue screen comes up
Keep in mind that there aren't any other app's running in the background that causes response time delays
The response time delays occur, regardless whether I am on Edge, Wi-fi or 3G.. I do not believe this to be a Networking issue...
Also, I only have 3- menu screens with maybe 23 app icons showing... most of which are iPhone apps like iTunes, Messaging, Settings, Mail, Safari, Stocks, weather, camera, contacts, calendar, pix, Maps, no games!!
I have done master reboot on phone... Network Reset... & Restore...
on rare occasions I will resume a 1-1.5 sec response time between my selections, otherwise, returning to 3-4 sec delays.
Coincidently, around the time this issue occurred, I had upgraded iTunes to 9.2 but doubt this created issues...I eventually downloaded r4.0 thinking a bug fix may have been included... but issue continued...
Any feedback? Thx

Well, to all those queing in on my question-observation... let me provide you an update.
True to form, APPLE provided me great support and Customer Satisfaction.
I did my due diligence and called into Apple Care and an app't was made for me at the Genius Bar the next day.
They assessed my situation and despite informing me it was the nature of the beast (3G), they happily exchanged my 3G out for a new 3G and guess what... with no app's sync'd to it as yet, right out of the box, not r4.0 the response time was the same.
Bottom line is 3G processor's are slow... especially compared against the 3GS and iP4... and loading r4.0 didn't impact it. With my contract expiring in a few days I bit the bullet and have a new iP4 and now enjoy almost instantaneous response to my key selections, etc.... oh, and no dropped calls due to antenna.

Strange response time for an RFC call viewed from STAD on R/3 4.7

Hello,
On our R/3 4.7 production system, we have a lot of external RFC calls to execute an abap module function. There are 70 000 of these calls per day.
The mean response time for this RFC call is 35 ms.
Some times a few of them (maybe 10 to 20 per day) are way much longer.
I am currently analysing with STAD one of these long calls which lasted 10 seconds !
Here is the info from STAD
Response time :                10 683 ms
Total time in workprocess : 10 683 ms
CPU time :                               0 ms
RFC+CPIC time :                       0 ms
Wait for work process           0 ms
Processing time           10.679 ms
Load time                            1 ms
Generating time                   0 ms
Roll (in) time                        0 ms
Database request time         3 ms
Enqueue time                      0 ms
Number      Roll ins            0
                 Roll outs           0
                 Enqueues         0
Load time   Program             1 ms
                  Screen              0 ms
                 CUA interf.          0 ms
Roll time    Out                 0 ms
                  In                  0 ms
                Wait                0 ms
Frontend    No.roundtrips       0
                  GUI time            0 ms
                  Net time            0 ms
There is nearly no abap processing in the function module.
I really don't uderstand what is this 10 679 ms processing time especially with 0 ms cpu time and 0 ms wait time.
A usual fast RFC call gives this data
23 ms response time
16 ms cpu time
14 ms processing time
1 ms load time
8 ms Database request time
Does anybody have an idea of what is the system doing during the 10 seconds processing time ?
Regards,
Olivier

Hi Graham,
Thank you for your input and thoughts.
I will have to investigate on RZ23N and RZ21 because I'm not used to use them.
I'm used to investigate performance problems with ST03 and STAD.
My system is R/3 4.7 WAS 6.20. ABAP and BASIS 43
Kernel 6.40 patch level 109
We know these are old patch levels but we are not allowed to stop this system for upgrade "if it's not broken" as it is used 7/7 24/24.
I'm nearlly sure that the problem is not an RFC issue because I've found other slow dialog steps for web service calls and even for a SAPSYS technical dialog step of type <no buffer>. (what is this ?)
This SAPSYS dialog step has the following data :
User : SAPSYS
Task type : B
Program : <no buffer>
CPU time                       0 ms
RFC+CPIC time              0 ms
Total time in workprocs    5.490 ms
Response time               5.490 ms
Wait for work process           0 ms
Processing time             5.489 ms
Load time                            0 ms
Generating time                   0 ms
Roll (in+wait) time                0 ms
Database request time          1 ms ( 3 Database requests)
Enqueue time                       0 ms
All hundreds of other SAPSYS <no buffer> steps have a less than 5 ms response time.
It looks like the system was frozen during 5 seconds...
Here are some extracts from STAD of another case from last saturday.
11:00:03     bt1fsaplpr02_PLG RFC     R     3     USER_LECKIT     13     13     0     0
11:00:03     bt1sqkvf_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
11:00:04     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     19     19     0     16
11:00:04     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     77     77     0     16
11:00:04     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
11:00:04     bt1sqkvf_PLG_18      RFC     R     4     USER_LECDIS     14     14     0     16
11:00:05     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     12     12     0     16
11:00:05     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     53     53     0     0
11:00:06     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     76     76     0     0
11:00:06     bt1sqk2t_PLG_18      RFC     R     0     USER_LECDIS     20     20     0     31
11:00:06     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     12     12     0     0
11:00:06     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     13     13     0     0
11:00:06     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     34     34     0     16
11:00:07     bt1sqkvh_PLG_18      RFC     R     0     USER_LECDIS     15     15     0     0
11:00:07     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     13     13     0     16
11:00:07     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     19     19     0     0
11:00:07     bt1fsaplpr02_PLG RFC     R     3     USER_LECKIT     23     13     10     0
11:00:07     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     38     38     0     0
11:00:08     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     20     20     0     16
11:00:09     bt1sqkvg_PLG_18      RFC     R     0     USER_LECDIS     9 495     9 495     0     16
11:00:09     bt1sqk2t_PLG_18      RFC     R     0     USER_LECDIS     9 404     9 404     0     0
11:00:09     bt1sqkvh_PLG_18      RFC     R     1     USER_LECKIT     9 181     9 181     0     0
11:00:10     bt1fsaplpr02_PLG RFC     R     3     USER_LECDIS     23     23     0     0
11:00:10     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     8 465     8 465     0     16
11:00:18     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     18     18     0     16
11:00:18     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     89     89     0     0
11:00:18     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     75     75     0     0
11:00:18     bt1sqkvh_PLG_18      RFC     R     1     USER_LECDIS     43     43     0     0
11:00:18     bt1sqk2t_PLG_18      RFC     R     1     USER_LECDIS     32     32     0     16
11:00:18     bt1sqkvg_PLG_18      RFC     R     1     USER_LECDIS     15     15     0     16
11:00:18     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
11:00:18     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     14     14     0     0
11:00:18     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     69     69     0     16
11:00:18     bt1sqkvf_PLG_18     RFC     R     5     USER_LECDIS     49     49     0     16
11:00:18     bt1sqkve_PLG_18     RFC     R     5     USER_LECKIT     19     19     0     16
11:00:18     bt1sqkvf_PLG_18     RFC     R     5     USER_LECDIS     15     15     0     16
The load at that time was very light with only a few jobs starting :
11:00:08 bt1fsaplpr02_PLG RSCONN01                     B 31 USER_BATCH     39
11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 31 USER_BATCH     34
11:00:08 bt1fsaplpr02_PLG /SDF/RSORAVSH                B 33 USER_BATCH     64
11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 33 USER_BATCH     43
11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 34 USER_BATCH     34
11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 35 USER_BATCH     37
11:00:09 bt1fsaplpr02_PLG RVV50R10C                    B 34 USER_BATCH     60
11:00:09 bt1fsaplpr02_PLG ZLM_HDS_IS_PURGE_RESERVATION B 35 USER_BATCH    206
I'm thinking also now about the message server as there is load balancing for each RFC call ?
Regards,
Olivier

How to check which RFCs causing issues in the system and RFC response times

Hi,
We have an issue with the RFC response times in CRM and need investigstion. We need to know which Which RFCs causing issues and how we can solve the problems.
Regards

Hi,
chek the below code
CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_EXIST
EXPORTING
FILE = W_FILENAME
RECEIVING
RESULT = W_RESULT
EXCEPTIONS
CNTL_ERROR = 1
ERROR_NO_GUI = 2
WRONG_PARAMETER = 3
NOT_SUPPORTED_BY_GUI = 4
others = 5.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-* MSGNO WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF W_RESULT IS INITIAL.
CALL METHOD CL_GUI_FRONTEND_SERVICES=>DIRECTORY_EXIST
EXPORTING
DIRECTORY = W_FILENAME
RECEIVING
RESULT = W_RESULT
EXCEPTIONS
CNTL_ERROR = 1
ERROR_NO_GUI = 2
WRONG_PARAMETER = 3
NOT_SUPPORTED_BY_GUI = 4
OTHERS = 5.
IF SY-SUBRC <> 0.
ENDIF.
ENDIF.
IF W_RESULT = 'X'.
RC = '1'.
ELSE.
RC = '0'.
ENDIF.
reward if helpful.
Regards,
nagaraj

CPIC/RFC Time vs Total Response time

Similar Messages

Maybe you are looking for