Skip to Content

Latency is how long it takes for the data to travel between its source and destination, measured in milliseconds.

One of the ways to optimize the C4C network performance is to minimize latency across the entire network. C4C offers a method to perform network testing using the SAP Cloud for Customer network diagnostic tool, which measures the HTTP latency and bandwidth from the browser all the way to the tenant at the application layer. This tool can be accessed by adding the below portion in red to your tenant 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

Latency1.png

  • 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

Latency2.png

How to interpret the information from these two tests:

Latency KPIs:

For Cloud for Customer the following latency guidelines have been established:

  • Under 100 ms if the tenant data center is in the same continent as the client
  • Under 250 ms for the total latency from end user to C4C

The bigger this number is, the bigger the overhead in performance and impact on end_user experience. Further, if we see a 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

Latency3.png

The previous example clearly 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 users and type of activities, which make use of this shared connection. In general, a bandwidth of 1 Mbps could be enough for a small trial implementation as a minimal recommendation. In some cases, if not other activities are running, 0.5Mbps might be enough, though it will not provide the best performance). As an example, the screenshot below shows a download bandwidth of less than 0.5 Mbps which could start causing degradation of performance

Latency4.png

 

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply