SAP Cloud for Customer: How-to identify cold browser scenario
Browser caching is a common technique used to optimize performance of web applications. In SAP Cloud for Customer, we cache the following at the browser level: HTTP statistic assets – like images, CSS files, Java Scripts, etc. and screen designs aka. Floor Plan metadata. Floor Plan metadata is the heaviest asset. This cached data is persisted for 14 days within the browser cache to improve performance and reduce network traffic. When browser cache is cleared all static assets are removed and the browser has to retrieve them from the server increasing network round trips and possible impact by poor network conditions, etc. which at the end represent higher response time and poor user experience.
Using HTTPWatch’s Basic Edition (free version – Download | HttpWatch), it is very easy to identify cold browser scenarios (with empty browser cache). Basically most of the GET requests in SAP Cloud for Customer should normally be cached at the browser and if we see GET requests that get sent to the server rather taken than from the cache – this will indicate a cold browser scenario.
Screenshot below shows an example of cleared cache. We can observe GET request, or several GET requests (Method column=GET) that went all the way to the server (Result column = ‘200’). In this specific case we are requesting screen design from the server (floor plan metadata).
The following screenshot shows the same step executed with static content cached (GET request has result column = ‘Cache’). We can see that request taken from the cache is very fast and took just 44 ms compared to 2.5 seconds before.
As you can see performance impact is very significant just for one GET request for floor plan metadata. The data received over the network is also significant – 232913 bytes compared to 0 when it is taken from cache.
In case you see cold browser behavior all the time (after the first time use) then, there could be a problem with the cache settings in your browser or IT maybe deleting the same via an Active Directory rule.
Verify that the browser cache is not deleted when it is closed. The following Internet Explorer configuration controls this behavior.
Verify with your IT department that there are no active directory policy rules, which clears browser cache.
Example: Microsoft Internet Explorer settings
Please navigate to:
User Configuration> ‘Administrative Templates’> ‘Windows Components’> ‘Internet Explorer’> ‘Internet Control Panel’> ‘Advanced Page’ – ‘Empty Temporary Internet Files Folder when browser is closed’
Verify that browser cache settings are optimal.
For more details of recommended browser settings, refer to the following link: