Performance Improvements in 1705

The following new feature(s) and improvements are available in 1705.

  • Avoid cold starts by disabling Implicit personalization
  • Browser Performance Optimizations due to uptake of SAP UI5 ver. 1.44 libraries
  • Smoother Page Scrolling & Reduction in response times while scrolling on lists for the Fiori Client

Please visit blog below for more details on the improvements.

Performance Improvements in SAP Hybris Cloud for Customer – 1705

For previous updates please see below:


End to End Performance

Welcome to the home of C4C Performance! We will continuously provide content related to performance including webinars, best practices, and how-to blogs.

Performance is one of the most important aspects of any Software as a Service (SaaS) application like SAP Hybris Cloud for Customer. However, sometimes factors like complex customizations in implementations and suboptimal client or network conditions can lead to a deterioration in end-to-end performance.


Factors Affecting End-to-End Performance


End to End performance is a complex subject and it consists of the following factors:



Listed below are several types of content covering the performance topic. Please use the comments area of the specific content for any questions or feedback you may have.



❗ Recorded May 31st, 2016: C4C Performance Best Practices

(Correction: In the video, the short url for the performance landing page (this page) is and not


Link to presentation





1. WDPDIPSAP Cloud Application Studio Performance Recommendations (Germany)

How-To Guides


The HowTo guides include troubleshooting and helpful tips on performance. They are categorized under Client, Server and Network respectively.





1. How to troubleshoot cold browser interactions: In this blog, we discuss how to identify cold browser scenarios. This is one of the most common causes of slow performance.


Please follow along the steps described in the blog below on how to monitor cold browser situations using in-tenant reports.

Monitoring for Cold Browser using In-Tenant Reporting

2. Troubleshoot performance impacts due to multiple embedded components in a facet/tab:

Too many embedded components on one facet can impact performance, especially when used in the landing facet or tab. Additionally, mashups, if not designed properly, can cause slow rendering of screens.

3. How-to troubleshoot high rendering time in the browser:


High rendering times on the browser can be caused by a slow disk system. This is due to the fact that like any SaaS application, SAP Hybris Cloud for Customer (C4C) relies on browser cache to store static content (not business data). The static content includes JavaScript, CSS, images. When the disk system is slow, the browser takes a long time to read from the disk and render it on the screen. Slow disk systems can be caused, ranging from temporary background programs running like anti-virus scans to problems with virtual machine setup.




1. How-to identify sub-optimal reports:

SAP Cloud for Customer comes with its own analytical reporting features, capabilities, and strengths. These capabilities should not be compared with other primary (independent) reporting / analytical tool, proper evaluation should be done to design and implement each business reporting use case optimally. Inefficient report or data source modeling may result in extremely slow report performance.

2. How-to analyze customization impact on server time


Tools like HTTPWatch and In Tenant Reporting provide a limited breakdown of the overall processing time into the client, network, and backend. There are however no further details about the backend processing, how customizations and integrations impact the performance. This can be accomplished via a custom report based on the same data source that powers the In Tenant Reporting




1. How-to troubleshoot network problems


As the number of components, networks and geographies increase, the probability of network failures increase as well and with this the end user experience or performance of the SaaS solution could be affected.


Optimize the Performance of your Cloud for Service implementation


Part 1:

Optimize the performance of your Cloud for Service implementation – Part 1


Part 2:

Optimize the performance of your Cloud for Service implementation – Part 2–part-2

To report this post you need to login first.


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

  1. Subhasish Roy

    Hi Guys,

    I ran the Response Time Analysis report to monitor the performance based on user interactions.

    But in the screen column I’m getting outputs like # , {0}.

    What screen does this refers to?

    Can you please help.



    1. Arun Kumar Reddy Janga

      Hello Subhasish,

      Screen name # wont be there from 1608 onwards.

      Till 1608, you can focus on records with screen name other than #

      Screen name {0} points to account screen. We will improvise in next releases to show proper screen name in this case..


      1. Subhasish Roy

        Thanks Anil.

        Is there anyway we can get the User ID in the output of the report?

        The Used ID is selected in the characteristics to be displayed in the report but still I’m not able to see it in the report.



        1. Arun Kumar Reddy Janga


          Is User ID empty?

          If it is empty, first you need to enable user id and IP address capturing.

          You can do this in Business Configuration.

          Administration -> Performance and Usage Monitoring -> Performance and Usage Monitoring -> User ID and IP tracking

          After its enabled, user id will be captured from that time.



          1. Subhasish Roy

            Hi Arun.

            Need some help.

            We have a report that is running slow.

            Is there anyway I can run the Response Time Analysis for a specific report?



          2. Subhasish Roy

            Hi Arun,

            Also facing another issue.

            Before running the report I have added the field User ID to be displayed in the report , but its not showing up after executing the report.

            Is there anything I have missed?



  2. Kanthimathi Krishnan

    Excellant information. This is a great source of information, having this as a basis we are starting the performance analysis of our tenants.

    Thanks for the great asset.



  3. Radek Stefaniak


    are there any statements about how many products and or customers we can utilize in C4C to not break performance? or this is very scalable?

    I guess with high number of those we should more utilize saved default queries for sure.

    1. Guru Shetti Post author

      Hello Radek,

      First of all my apologies for the really late response! (But better late than never)

      To answer your question, yes the solution is very scalable! If you want more details please drop a note to your CEE.




Leave a Reply