What's changed: Created AZ-120 Chapter 4 (Domain 4 first-half: performance/cost optimization (Azure Advisor recommendations, VM resizing, Reserved Instances vs Savings Plans, storage cost, archiving); network and app/DB optimization (Azure Network Watcher for latency/throughput, proximity/Accelerated Networking/VM size, app-server horizontal/vertical scaling, DB tuning, continuous-improvement cycle)).
4.2Network and app/DB optimization
Understand analyzing/optimizing network performance, identifying latency/throughput bottlenecks, and continuously tuning/scaling SAP application servers and databases.
SAP performance depends on the app-tier↔DB-tier network and each tier’s resources. Continuously measure, identify bottlenecks, and optimize.
4.2.1Network performance optimization
Measure network latency and throughput (visualize paths/latency with Azure Network Watcher / Connection Monitor) and identify bottlenecks against SAP requirements. Remedies include enabling Accelerated Networking, using a proximity placement group to co-locate app↔DB, adjusting to an appropriate VM size (NIC bandwidth scales with VM size), and revisiting ExpressRoute bandwidth. For "high app↔DB latency," revisit proximity/Accelerated Networking/VM size.
4.2.2App server and DB optimization
Scale SAP application servers horizontally (add app instances) or vertically (VM resize) for throughput per load. Tune the database (HANA, etc.) with the right VM (memory/CPU), storage (IOPS/throughput, Write Accelerator), and index/partition design. Run a continuous-improvement cycle (measure → identify bottleneck → optimize → re-measure), leveraging insights from Azure Advisor and Azure Monitor.
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.