SAP S/4HANA Administration · System Architecture & Instances

A work process is consuming huge heap memory and then gets killed and restarted — what is the chain of events, and why heap rather than the normal pool?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in System Architecture & Instances

The enqueue server holds its lock table in the memory of the central services instance — what does that storage choice imply if that instance restarts without protection?

You suspect ONE specific dialog instance (not the one you're logged into) is saturating its work processes — which of SM50 / SM66 / SM51 gets you there fastest?

How many message servers exist in a system, and why does that count make logon load balancing a single point of dependency?

A colleague insists the primary application server (PAS) must never be taken offline because it is functionally special — are they right?

If ABAP loads live in the database (not on each app server's disk), what does that explain about a freshly started instance's first-access performance?

A teammate wants to bounce all three landscape systems together because they 'share infrastructure' — what's wrong with that mental model?

Start learning today

Free to start — download the app or use it in your browser.