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.
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 http://bit.ly/c4cperformance and not bit.ly/c4cperf)
1. WDPDIP – SAP Cloud Application Studio Performance Recommendations (Germany)
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.
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.
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 timehttp://scn.sap.com/community/cloud-for-customer/blog/2016/05/28/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
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
Optimize the performance of your Cloud for Service implementation – Part 1http://scn.sap.com/community/cloud-for-customer/blog/2016/06/15/how-to-optimize-the-performance-of-your-cloud-for-service-implementation
Optimize the performance of your Cloud for Service implementation – Part 2http://scn.sap.com/community/cloud-for-customer/blog/2016/06/22/optimize-the-performance-of-your-cloud-for-service-implementation–part-2