Ansicht
Dokumentation
05099 - Page Faults - Any Setting with SAP to Reduce Non-DB PAge Faults
Fill RESBD Structure from EBP Component Structure BAL Application Log DocumentationThis documentation is copyright by SAP AG.
Page Faults - Any Setting with SAP to Reduce Non-DB PAge Faults
Our DB Server is a 9406-730 with 13gig memory. We have all userslogging on to two app servers, we try not to have any users on the DB
server. Our DB server 3 memory pools, *Machine=1gig, *Bsse=11.9gig,
*Spool=.1gig. We are running 4.6C on V4R5M0 with all the latest
PTF's. In the *Base pool the Max Active value is set at 200, we have
alot of Active-> Wait (5000-7000) but the Wait->Inel is 0. Our SAP
response time is not very good, slow is the best to describe it with
real slow at times.
We basically have 12gig in *BASE which runs SAP. Our Non-DB page
faults average 200-400 per second (via wrksyssts) and will sometimes
peak 1000-2000 per second. I've read in various notes and manuals
that the SAP memory definitions such as Program Buffer, Paging Area,
Extended Memory, Number of WP's do not affect System Performance. Is
this a true or did I just misunderstand what I've seen? Are there SAP
buffers or other setting which I may have oversized and is causing
the high Non-DB page faults? The sizing tools we've used indicates
12gig should enough. Before we go and purchase more memory we'd like
to know if something can be cahnged to rduce the amount of memory we
are currently using. How much memory are others running on the DB
server?
Durban Tours - Südafrika Safari
General Material Data TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 1748 Date: 20240420 Time: 160813 sap01-206 ( 4 ms )
