How to idetify high network latency and bandwidth within SAP Cloud for Customers

Perform network testing using the SAP Cloud for Customers network diagnostic tool. Within SAP Cloud for Customer we have we have a small tool which measure the HTTP latency and bandwidth from the browser all the way to the tenant at the application layer level. This tool can be access using the following URL:

https://myXXXXXX.crm.ondemand.com/sap/public/ap/ui/repository/BYD_COD/Common/Diagnostics/diagnostic_tests.html

This tool offers two test options:

• Start Latency Test. This option executes 10 HTTP latency tests and then offers the average latency for the 10 tests. This type of test should be executed multiple times during the day to get multiple samples and capture multiple readings throughout the day for the network latency

• Start Download Test. This option test the download bandwidth and the latency giving samples for five executions. This type of test should be executed multiple times during the day to get multiple samples and capture multiple readings throughout the day for the network bandwidth

How to interpret the information from these two tests:

• HTTP Latency Test. In general the average latency should be less than 250 ms, the bigger this number is, the bigger the overhead in performance and impact on end user experience. Also if we see sporadic increase, this could mean a high jitter and with this a symptom of some other kind of problem like bandwidth congestion, overhead in forward proxy, overhead in some network component within the path used to connect to the SAP Cloud System. The following example shows a sudden increase in latency, which if we see this happens constantly this for sure will present a problem

                    The previous example clear shows a problem where the average latency shows 1.1 seconds with even one reading which was over 6.4 seconds.

• Bandwidth Test (Download Test). As it was mentioned before, bandwidth is a factor relevant to the type of applications, number of user and type of activities, which make use of this share connection. In general bandwidth of 1Mbps could be enough for a small trial implementation as a minimal recommendation, in some cases if not other activities are done at least 0.5Mbps (should be enough but it will not provide the best performance). By example the screenshot below shows a download bandwidth of less than 0.5 Mbps which could start causing degradation of performance