Performance issues on a JS Storefront application will be in the form of response time degradation or full outages caused by resource exhaustion. It can be challenging to identify the root of the problem since there are many components involved, as illustrated below:
A request will involve the components below, all of which could be the source of the problem:
- Client (browser or CDN)
- Apache web server (through JS Storefront vhost)
- Nginx web server (jsapps container of the jsapps pod)
- Server.js (jsapps-ssr container of the jsapps pod - only relevant when SSR mode is enabled)
- CDN (not illustrated above, but if a CDN is used then it would sit on this level - the request could end here or continue to the origin server if a cached response is not found)
- Apache web server (through API vhost)
- Commerce web services (API pod)
In depth performance troubleshooting guidelines can found in KBA 3059689 - How to Troubleshoot Common Performance Problems on Commerce Cloud Using Dynatrace, which can be especially useful if the bottleneck is found on the apache, API or database layers. This article focuses principally on the JS Storefront layer.
JS Storefront on Commerce Cloud.
spartacus, TBD , KBA , CEC-SPA , SAP Commerce Cloud Spartacus , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.