SAP Fiori – Performance
This is a collaborative document to share lessons learned contents for the SAP Fiori Performance topics in the community SAP Fiori.
Please feel free to insert the link of your document or blog by selecting the edit button from Actions.
1. Performance tips
- Apply the latest Support Package.
Performance improvements have been included in the latest support packages for each app. Double check that you have applied the latest support packages.
http://support.sap.com/swdc - 2149291 – Performance issues on initial loading of SAP Fiori launchpad
- Set Metadata Cache in the production Gateway server.
- For Mobile and Tablet, use SAP Fiori Client app.
- Discussion in SCN: How to do performance testing of a standard fiori application?
- Performance and Scalability on Service Marketplace: http://service.sap.com/performance
2. Understanding the cache management
3. Tools: Finding the bottleneck
Please look at How to do basic Performance Analysis of SAP Fiori based UIs in SAP Service Marketplace.
- Frontend
- Chrome Developer Tool: Timeline – Chrome timeline is a handy tool to check the timeline for Loading, Scripting, Rendering and Painting.
Probably you can find that some of OData service calls took longer time.
- Chrome Developer Tool: Timeline – Chrome timeline is a handy tool to check the timeline for Loading, Scripting, Rendering and Painting.
- HTTPWatch – HttpWatch integrates with Internet Explorer and Firefox browsers to show you the HTTP and HTTPS traffic. It’s a little bit more user-friendly than the embedded tools. Trial version exists.
- Backend
- OData Performance Trace: /IWFND/TRACES and /IWBEP/TRACES
Performance Trace – SAP NetWeaver Gateway – SAP Library
- OData Performance Trace: /IWFND/TRACES and /IWBEP/TRACES
- Single Activity Trace: SAT
Configuring SAT – SAP Virtual Machine Container – SAP Library
Displaying SAT Results – SAP Virtual Machine Container – SAP Library
- ABAP Performance Trace: ST12, ST05
Performance Trace Overview – ABAP Test and Analysis Tools – SAP Library
Single Transaction Analysis (ST12) – getting started
4. Tips when you develop a custom app
- Look at the SAP Fiori Design Guidelines.
- Performance Best Practices – SAP NetWeaver Gateway – SAP Library
- Gateway Performance Best Practices – How to consume Gateway from performance point of view
5. Testing tools
Great one Masa!
This collection of tips, tricks and things to watch out for is SO important. thanks you so much Masa!!
I wish we can keep it "live" and the community can contribute more as we go
Well explained, the new topic Masa !
Nice, any idea, if we can track whether the transactions are done from fiori application or backend tcodes ?
Say, if a customer wants to check if the apps are used by their users or not.
Regards,
Tejas
Nice idea Tejas, we had the same request but a question off that, why would the user have access to something they dont use? If they dont use the app, it shouldnt be in a business process, which in turns means the user shouldnt have it.
What I meant was a Utility so that Business administrator can check if Fiori apps developed for the business users are utilized or they are still using the traditional approach (via GUI or tcode). This helps them to track the usage via Fiori apps. Some reporting tool which shows the percentage of users migrated to new UX.
Thanks for sharing Masa, I wonder how much beautiful things you have in your store.
Thanks,
Warm Regards
Hemendra
Thanks for your kindly sharing, It's very useful.
Thanks for valuable suggestion which help us ...
Hi Masa, Nice post!
But I think it's worth to metion ST12 Trace and HTTPWatch tools too.
Please feel free to update. This is a collaborative document.
Thanks for sharing, really nice blog!