We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.
Showing posts with label Rates. Show all posts
Showing posts with label Rates. Show all posts

AS/400 Checking Page Fault Rates

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Prerequisites

If there is data already in main memory, it can be referred to independent of the memory pool in which it is stored. However, if the necessary data is not available in any memory pool, it is brought into the same memory pool as the job that refers to it. (This is described as page faults.) When data is transferred into a memory pool, other data is moved, if it is being changed, and is automatically stored in the auxiliary memory. (This is described as paging.)

Procedure

Under OS/400: Pages in = Pages out.

Since page defaults hinder performance, the memory pool must be large enough to keep paging to an acceptable amount.

Value limits for page faults under OS/400

If in Transaction ST06 or on the CCMS Alert Monitor you notice a high page default rate in a memory pool, enlarge this pool.

Pool

Value Limit:

Machine pool (always system pool 1)

Since the machine pool contains objects used across the whole system, page faults in the machine pool affect all the jobs in the system. For this reason, ensure that the page fault rate is as low as possible in this pool.

Value limit: 10 page faults per second

Other pools

For optimum performance, an average rate of 2 page faults per second for each active work process should not be exceeded.

The upper limit that should not be exceeded is a rate of 20 page faults per second for each active work process.

(see example below)

The following examples can help you when determining page fault rates in your system:

Best Performance:

Number of active work processes: (AS/400 jobs with status RUN)

10

Number of page faults for each active work process

2 faults per second

Permitted

20 page faults per second

Paging overhead for each work process (assumed average response time of the hard disk is 10 millisec.)

20 millisec. per second

This corresponds to a paging overhead of 2%.

Upper Limit

Number of active work processes: (AS/400 jobs with status RUN)

10

Number of page faults for each active work process

20 faults per second

Permitted

200 page faults per second

Paging overhead for each work process (assumed average response time of the hard disk is 10 millisec.)

200 millisec. per second

This corresponds to a paging overhead of 20%. The 20% limit should not be exceeded.



Keyword: BASIS
Title : AS/400 Checking Page Fault Rates

Windows NT Checking Page Fault Rates for SAP R/3

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Prerequisites

If the operating system is not occupied with other functions, all the pages in the working memory that are not in the address area of an active work process are swapped out (lazy page out) of the operating system as a preventive measure. If space is then required, the pages already swapped out only have to be deleted.

In a performing system, Transaction ST06 thereby displays a high Pages out value and a small Pages in value in relation. This indicates that many of the swapped out pages were not overwritten and could not be included again through a work process without a page file access. Therefore, only the Pages in value is very important when assessing system performance.

See: Special Features under Windows NT

Procedure

The following values for Pages in should not be exceeded in the short or long-term.

Value Limit: Pages in under Windows NT

Pages in

Value Limit:

Short-term maximum for Pages in/s (Transaction ST06)

200

Long-term maximum for Pages in/h (Transaction ST06)

600.000

A high Pages out value has no bearing on system utilization. Only the Pages in value is used as a measure of system utilization. If the value limits are exceeded, this an indication that the memory capacity of the machine is too small.



Keyword: BASIS
Title : Windows NT Checking Page Fault Rates for SAP R/3

UNIX Checking Page Fault Rates BASIS

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Prerequisites

Unlike Windows NT, pages are swapped out to the working memory under UNIX if the space is needed, and then they are overwritten. This swapping out uses up valuable time and performance.

Transaction ST06 displays a small Pages out value and a similar Pages in value in a performing system. The Pages out value is very important when assessing system performance.

Procedure

The following values for Pages in should not be exceeded in the short or long-term.

Value Limit: Pages out under UNIX:


Pages in

Value Limit:

Short-term maximum for Pages in/s (Transaction ST06)

200

Long-term maximum for Pages in/h (Transaction ST06)

600.000



Keyword: BASIS
Title : UNIX Checking Page Fault Rates BASIS

Checking Page Fault Rates for SAP r/3

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

The following graphic displays the screen for transaction ST06. In the first screen, the current values for Pages in/s and Pages out/s are listed (in the following graphic under the heading Memory ).

To display the selection screen for more detailed information, choose Detail analysis menu. To get a list of the Pages in and Pages out values in the past 24 hours, in the block Previous hour choose Memory. The following screen displays this report.

You can find operating system-dependent checks in the following sections:

UNIX

Windows NT

AS/400



Keyword: BASIS
Title : Checking Page Fault Rates for SAP r/3

T r a n s l a t e to your language