As with every new release we are very excited to announce the following performance related updates in 1708.
1. Improved performance in mobile offline and low bandwidth scenarios
In 1708 we have introduced the ability to compress request payloads. Typically responses are always compressed and to further optimize performance, requests originating from the client will now will also be compressed. We can think of this as of as, all the user input details such as line items, ticket details as being part of the request payload.
This feature will be activated after the initial 1708 rollout in a later hotfix. Request compression will especially be valuable in low bandwidth conditions such as mobile. In mobile offline scenarios for instance (chart below) we have seen a 33% improvement synchronizing opportunities on 3G network.
Fig-1: Performance improvement in mobile offline scenarios when compressing request payload.
Additionally this should help in lower bandwidth and battery usage while using mobile devices.
2. Faster page load times in cold browser scenarios
Before 1708, static content like images, JavaScript files and other assets used to be downloaded from the C4C tenant itself and subsequently cached on the local browser in the client's disk. This is also called as cold browser, when static cacheable objects have to be retrieved over the network from the C4C server. This can typically happen when a user explicitly deletes the cache or has a setting enabled that automatically deletes browser cache. This can also happen after an upgrade or an hotfix. Based on the chart below we can see that when a user is located far away from the data center from where their tenant is located, the network latency increases. Therefore page load times can be 5X (times) slower in places where a user is located far away.
Fig-2: typical login pageload times vs distance from the data center
Therefore in 1708, we have introduced CDN (content delivery network) for static objects. CDN's work on the principle of delivering content from a server close to a user as with better network peering with local network carriers. Therefore if a user is located in Sydney and the tenant data center is in Germany, then, the static content will be delivered out of a server near Sydney with much lower network latency. Please note business content will still be delivered by your original tenant URL and not by the CDN. No business data will be made available to the CDN servers. In cold browser scenarios we have seen CDN performance to be as much as 5-10 times compared to one without CDN. Please see video below for a demo visualizing the same.
Video: Demo comparing login pageload performance comparing with and without CDN (best viewed in full screen).
1. Improved performance in mobile offline and low bandwidth scenarios
In 1708 we have introduced the ability to compress request payloads. Typically responses are always compressed and to further optimize performance, requests originating from the client will now will also be compressed. We can think of this as of as, all the user input details such as line items, ticket details as being part of the request payload.
This feature will be activated after the initial 1708 rollout in a later hotfix. Request compression will especially be valuable in low bandwidth conditions such as mobile. In mobile offline scenarios for instance (chart below) we have seen a 33% improvement synchronizing opportunities on 3G network.
Fig-1: Performance improvement in mobile offline scenarios when compressing request payload.
Additionally this should help in lower bandwidth and battery usage while using mobile devices.
2. Faster page load times in cold browser scenarios
Before 1708, static content like images, JavaScript files and other assets used to be downloaded from the C4C tenant itself and subsequently cached on the local browser in the client's disk. This is also called as cold browser, when static cacheable objects have to be retrieved over the network from the C4C server. This can typically happen when a user explicitly deletes the cache or has a setting enabled that automatically deletes browser cache. This can also happen after an upgrade or an hotfix. Based on the chart below we can see that when a user is located far away from the data center from where their tenant is located, the network latency increases. Therefore page load times can be 5X (times) slower in places where a user is located far away.
Fig-2: typical login pageload times vs distance from the data center
Therefore in 1708, we have introduced CDN (content delivery network) for static objects. CDN's work on the principle of delivering content from a server close to a user as with better network peering with local network carriers. Therefore if a user is located in Sydney and the tenant data center is in Germany, then, the static content will be delivered out of a server near Sydney with much lower network latency. Please note business content will still be delivered by your original tenant URL and not by the CDN. No business data will be made available to the CDN servers. In cold browser scenarios we have seen CDN performance to be as much as 5-10 times compared to one without CDN. Please see video below for a demo visualizing the same.
Video: Demo comparing login pageload performance comparing with and without CDN (best viewed in full screen).
- SAP Managed Tags:
2 Comments
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
