Professional Documents
Culture Documents
2020 - 002075129400005881672020 - BAD Performance
2020 - 002075129400005881672020 - BAD Performance
Communication
09.09.2020 11:40:18 CET - Problem Description: Ahmed abdallah (S0020292576)
Dears,
We had a bad performance and we want to know the reasons for this case.
connection is open
Dear Customer,
I am logged on checking your system and I will update you ASAP with my findings.
Kind regards,
Vanessa
SAP Product Support.
Dear Customer,
I am no longer able to connect to your system - is the system up and running? When logged on I could see high response times in
SMLG and also checking the workload in ST03 for the last 4 hours there was some high processing time and frontend/gui time - the
DB time was low. I did some basic checks but I have more analysis to do and would like to capture some traces if performance is
still slow. Please let me know the current status of the system and also provide a 24*7 phone number so I can call you to discuss.
Please also check the network between frontend and the application server - NIPING tool can help see note ## 2330380 - Remote
Client Performance
Kind regards,
Vanessa
SAP Product Support.
Dear Customer,
If you can provide a contact number where we can reach you to discuss it will help with speeding up our analysis process.
In any case our findings so far are that the main slowdown occurred 10:50 -12:10 system time today. A slow down/communication
issue with the database meant that DB commits and some DB requests were impacted. This then caused a work process
bottleneck as there are only 10 dialog work processes available. The STAD records below highlight this:
Request time 8 ms
Commit time 35.309 ms
DB Proc. Time 0 ms
NEXT STEPS:
Increase dialog WPs available - there is no resource issue with CPU on your system and lack of WP
resources escalated the issue further, please add 5 new dialog WPs.
Running the minichecks report highlighted I/O issue which are a possible cause of the high commit times:
M0312 I/O read latency data max. (ms, last day) proddb1 865.74 <= 20.00 X 1999930
M0313 I/O read latency data avg. (ms, last day) proddb1 7.08 <= 10.00 1999930
M0314 I/O read reload throughput avg. (MB/s) proddb1 n/a >= 200.00 1999930
M0315 I/O write throughput data min. (MB/s, last day) proddb1 2 >= 20 X 1999930
M0316 I/O write throughput data avg. (MB/s, last day) proddb1 7 >= 100 X 1999930
M0312 I/O read latency data max. (ms, last day) proddb1 865.74 <= 20.00 X 1999930
M0313 I/O read latency data avg. (ms, last day) proddb1 7.08 <= 10.00 1999930
M0314 I/O read reload throughput avg. (MB/s) proddb1 n/a >= 200.00 1999930
2000000 - FAQ: SAP HANA Performance Optimization in particular the section 11. How can the performance
of commit operations be optimized?
I would ask you to Schedule SDF/SMON as per KBA 2651881 How to configure SMON for performance
monitoring and analysis. That way if the issue reoccurs we can have some important information collected.
Kind regards,
Vanessa
Contacts
Secondary
Role Name Time Zone Primary Phone E-Mail
Phone
osayed@ecc-
Osama El Sayed
Reporter CET eg.co
(S0019374268)
m
aabdallah@ecc-
Ahmed Abdallah
Created By CET +20-1111555350 eg
(S0020292576)
.com
osayed@ecc-
Osama El Sayed
24h Contact CET eg.co
(S0019374268)
m
osayed@ecc-
Osama El Sayed
System Opener CET eg.co
(S0019374268)
m
KBA/SAP Notes
Action Log
0020751294
Ahmed abdallah
11:40:18 CET Incident created 0000588167
(S0020292576)
2020
Ahmed abdallah
11:40:18 CET Priority changed Medium Very High
(S0020292576)
Ahmed abdallah
11:40:18 CET Status Not Sent to SAP Sent to SAP
(S0020292576)
SAP Note
13:36:12 CET SAP 2144008
add./rem.
Memo/Text
13:36:12 CET SAP Reply
changed
Ahmed abdallah
13:46:44 CET Status Customer Action Sent to SAP
(S0020292576)
SAP Note
16:51:14 CET SAP 1999930
add./rem.
SAP Note
16:51:14 CET SAP 2000000
add./rem.
SAP Note
16:51:14 CET SAP 2651881
add./rem.
Memo/Text
16:51:14 CET SAP Reply
changed