By Caleb Billingsley, Performance Expert, Foulk Consulting
For decades, SAP performance conversations followed a predictable pattern:
System is slow → add CPU → add memory → tune SAP settings → repeat.
That model is gone.
As organizations move to SAP RISE or SAP workloads on hyperscalers, infrastructure control shifts away from IT teams and into a managed service model. You no longer decide when to scale hardware. You don’t choose the exact instance layout. In many cases, you don’t even see the OS.
What you’re left with is a black box, and the same business expectation: “The system has to be fast.”
This changes performance engineering fundamentally.
From Performance Tuning to Performance Governance
Traditional SAP performance work was about tuning the system.
In RISE, performance is about governing outcomes.
You can’t log into the host and tweak kernel parameters. You can’t just “throw more iron” at a Monday-morning slowdown. Instead, performance success depends on whether you can:
- Define clear, measurable performance expectations
- Detect degradation early
- Prove where responsibility sits: application, integration, or infrastructure
Performance governance becomes the discipline of managing performance across organizational and vendor boundaries, not just technical layers.
This is why performance in RISE fails when it’s treated as a one-time test instead of a continuous control.
Holding Cloud Vendors Accountable (Without Finger-Pointing)
One of the most common frustrations we hear is:
“SAP says the infrastructure is fine. Our business says the system is slow.”
Without data, that conversation goes nowhere.
In a RISE model, accountability comes from correlated performance evidence, not opinions.
What actually works today:
- Workload-based baselines (not synthetic vanity metrics)
- Time-aligned tracing across SAP, integrations, and user experience
- Repeatable test scenarios that simulate real business load patterns
Modern tools can already do this when used correctly:
- SAP workload statistics (ST03N / STAD equivalents in S/4)
- End-to-end transaction tracing
- External observability platforms capturing latency, wait time, and saturation signals
- Controlled performance tests executed before and after transports
The goal isn’t to “catch SAP” or the hyperscaler, it’s to establish a shared source of truth. When everyone is looking at the same data, resolution gets faster and escalation becomes constructive.
You Can’t Tune the Server, So You Tune What Matters
When infrastructure is off-limits, code and design decisions dominate performance outcomes.
In RISE environments, we consistently see performance issues driven by:
- Inefficient ABAP customizations
- Poorly written CDS views
- N+1 query patterns introduced during S/4 conversions
- Chatty integrations with third-party systems
- Background jobs colliding with business peaks
This is where “shift-left” performance becomes real, not theoretical.
Performance specialists don’t disappear in this model. They become shared service enablers, working with developers earlier:
- Reviewing custom code for performance risk before UAT
- Load-testing integration paths in ITC2 / ITC3, not just pre-go-live
- Teaching teams how to recognize performance anti-patterns in S/4
The best RISE programs treat performance expertise the same way mature organizations treat SRE or DevOps: centralized knowledge, decentralized execution.
Performance Testing Changes in RISE (But It Still Matters)
Performance testing in RISE is not about maxing out hardware anymore.
It’s about answering different questions:
- What happens when real users log in at the same time?
- Which transactions degrade first under load?
- Where does latency accumulate: frontend, application, database, or integration?
- What’s the business impact of a 20% slowdown?
This is why realistic workload modeling matters more than ever. You’re not testing capacity, you’re validating experience under constraint.
When performance testing is done well in RISE, it becomes the evidence layer that supports:
- Go-live decisions
- Vendor escalations
- Change approvals
- Ongoing optimization priorities
The Real Shift: Performance as a Business Control
The biggest mindset change we see is this:
Performance is no longer an IT tuning exercise. It’s a business risk control.
In a managed cloud world, success comes from:
- Clear expectations
- Continuous measurement
- Shared accountability
- Early intervention
RISE doesn’t eliminate performance problems, it just removes the illusion that hardware fixes everything. Organizations that adapt their performance strategy thrive in RISE. Those that don’t end up stuck in endless escalation calls with no leverage. And the difference almost always comes down to governance, not tools.
To move beyond being stuck in endless escalation calls and truly adapt your performance strategy for the managed cloud, you need a proactive, governance-led approach. If your organization is ready to shift its performance mindset from reactive tuning to strategic business risk control and establish the continuous controls necessary to thrive in SAP RISE, contact Foulk Consulting today to speak with Caleb or another member of our team.
