Web Platform Performance Guide

Overview
The Web Platform is a Node.js-based middleware application deployed as a Docker container. It serves the UI and connects to SAP ABAP backend systems. Performance can vary depending on deployment method, network conditions, and configuration.

1. General Performance Tips
Container settings

• Leave the log level at “info” to improve performance.
• Container restarts clear existing sessions, so that all users are forced to log in again. This can be prevented by using a persistent database, refer to the variables DATA_FOLDER and PRIVATEKEY.
  This does not work on BTP.
  

Reverse Proxy Configuration:

• Use caching headers and compression (e.g., gzip).
• Terminate SSL at the proxy level.
• Enable HTTP/2 for faster loading.
  

Network Optimization:

• Host the Web Platform close to the user base.
• Minimize DNS lookups and reduce round trips.
  

Browser Language Settings:

• Set “English (no location)” as the top language in browser preferences to reduce unnecessary locale-based loading delays. Inconsistent performance of the Web Platform across our global ActiveControl User Community
  

Resource Limits:

• Use User Preferences to restrict the size of ActiveControl Analysis Results (limit number of rows) to reduce load time and memory usage.
  

2. Deployment-Specific Performance Recommendations
SAP BTP Cloud Foundry

• Use BTP regions closest to your user base to reduce latency.
• Monitor container resource usage via BTP’s built-in tools.
  

Public Cloud Kubernetes (e.g., AWS EKS, Azure AKS, GCP GKE)

• Deploy in regions closest to users.
• Use reverse proxies like NGINX or Traefik for SSL termination and caching.
• Ensure that web sockets are allowed on route /ws and that relevant timeout parameters are set.
  

On-Premises Kubernetes (e.g., OpenShift, Rancher)

• Optimize cluster networking and DNS resolution.
• Ensure that web sockets are allowed on route /ws and that relevant timeout parameters are set.
• Use local caching and load balancing.
• Monitor with tools like Prometheus + Grafana.
  

Docker/Podman on Linux Servers

• Use NGINX or Apache as a reverse proxy.
• Ensure that web sockets are allowed on route /ws and that relevant timeout parameters are set.
• Ensure the server is geographically close to users.
• Monitor system resources (CPU, memory, disk I/O).
  

3. Telemetry and Monitoring

• The Web Platform supports OpenTelemetry.
• Recommendation: Connect to a telemetry solution such as:
• Grafana Tempo
• Jaeger
• Azure Monitor
• AWS CloudWatch
  

Benefits:

• Real-time performance insights.
• Faster troubleshooting.
• Usage analytics for optimization.
  

This article Web Platform Performance Guide and additional knowledge articles can be found in the basis technologies customer portal.