Ansicht
Dokumentation

05915 - Optimal performance

05915 - Optimal performance

rdisp/max_wprun_time - Maximum work process run time   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Optimal performance

Hi Chris,

there are several things you can do to improve performance.
I made the bitter experience that everyone first blames it on the
hardware, sometimes even the platform before looking for the reasons.

First be sure to get the latest PTFs according the INFO-APAR, the
current kernel patch level, that means also patches like LIBDBSL.
Then check wether your mirroring software needs additional PTFs.
Please delete the SAP SQL Packages using the command DLTR3PKG.
Then apply the latest Support Packages.
(That's what the hotline would answer if you opened a customer call.)

Then you should have a closer look at the Guide "SAP R/3 Installation
on AS/400" in concerns of "CHGIPLA CPRJOBTBL(*ALL)", system
authorisations and the OS/400 system values.

Be sure to give the maximum available main memory to the *BASE pool.
The *SYSTEM Pool should get enough memory to avoid a page fault rate
higher than 100 faults/sec. If you don't have (native AS/400)
interactive workload, give the memory of the *INTERACT share pool to
the *BASE pool by changing the subsystem QINTER.
--> CHGSBSD SBSD(QINTER) POOLS((1 *BASE) (2 *BASE))
Your will see the result with command WRKSYSSTS, *INTERACT will
dissappear as soon as all jobs are finished that use memory of that
pool.

[ Not recommended, but possible:
To give separated main memory to the production system you could use
a separate Share Pool and change the subsystem description
R3<SID>400/R3<instance>. ]

Next you should have a look at the corresponding SAP notes (44625,
103747, ...). Just search for "AS/400" and ("bufers"
or "performance") and pick the notes fitting for your SAP release.
If your system uses lot's of RFC you should search for notes
with "RZ12" and "RFC QUOTAS".

Then I would suggest to have a look at the transaction ST02 where no
swaps (except the programm buffer) should be reported.
In SM50 you should have a look at the CPU usage of the work
processes. If there are no DIA with almost no CPU time then you
should increase the number of workprocesses. This scheme also fits
for UPD and UPD2 WPs.

If you (or your technical SAP concultant) have done all this, you
should set up an early watch session (see SAP notes for RTCCTOOL).
The recommendations of the "technical core competence team" are very
helpful (except reducing the System value QBASACTLVL by forgetting
the work processes of additional SAP systems on the same computer,
and the warning that your system wouldn't have enough disc arms, if
you don't only use 4GB or 8GB discs).

Further analysis for the poor DIA performance could be done with
transaction ST03, ST03N, STAD, STAT, ST04, ST05 (tracing by
transaction, terminal, or user).

Often modifications are the reason for weak performance. Sometimes an
authorisation concept that wastes memory (especcially large user
menus in 4.6C or higher) is the reason. This can be seen in
transaction SM04 --> memory.

Reorganisation and data archiving (notes 16083, 48400, 391958, 41300,
48009, "IDOC", ...) are another important performance issue.


If nothing else works, a data collection with the AS/400 performance
monitor will show, wether processor- , disc- capayity, or main memory
ist the reason.

Best reguards
Jürgen Zeh
technical consultant

basycs GmbH - Basic Systems for Informatics


--- In SAP on System iZy..., "Sugg, Chris" <cgcsuggZn...> wrote:
> Thanks Fred.
>
> Most of the increase in ASP% is coming from 3 copies of our PRDDATA
library
> on the DEV/TST LPAR. One is for mirroring and the other 2 are for
our test
> clients. I will definately look at your suggestions to see if I
can improve
> the performance with the current configuration until more disk can
be
> purchased.
>
> Thanks again,
> Chris
>
> -----Original Message-----
> From: Fred Grunewald [mailto:fgrunewaldZv...]
> Sent: Monday, April 22, 2002 5:59 PM
> To: SAP on System iZy...
> Subject: Optimal performance
>
>
> Chris,
> From an iSeries standpoint, 80% utilization of an ASP has been the
key
> guideline for many years. However, with the larger disk arms
(storage
> units) capacities and any changes in extension allocations for
auxiliary
> storage may have moved that guideline up, I don't know. Unless
someone
> in the audience may challenge it, I would work with that. Having
said
> that, your server seems to be below that guideline so the next step
> would be to run the performance collector and understand where the
> bottlenecks in your server may be occurring. Key points to observe:
> - non-database faults in machine pool and *base (I have seen
> recommendations for all R3_<inst> subsystems run in *base pool ???)
> - arm utilizations (data may have "aged" or some drives)
> - CPU % at the times when poor DIALOG response occur
> - IOP utilizations for Ethernet adapter and DASD
> hope this helps,
> Fred L. Grunewald
> Vision Solutions, Inc.
> Rochester, MN 55901
> USA
> +1 507 292 9854
> +1 507 292 9855 Direct
> +1 507 252 1043 facsimile
> fgrunewaldZv...
>
> >From: "zcsugg"
> >Reply-To: SAP on System iZy...
> >To: SAP on System iZy...
> >Subject: RE: Optimal Performance
> >Date: Fri, 19 Apr 2002 17:55:51 -0000
> >
> >Does anyone know if SAP has an optimal performance level (ASP %)
for
> >the AS400? Currently, we are at 70% dor ASP used on a 740 sharing
3
> >processors between DEV/TST systems within the LPAR. response times
> >are at 2.5 to 7 seconds on average for DAILOG.
> >
> >Thanks,
> >Chris
> >
>
> Send and receive Hotmail on your mobile device: Click Here
> <http://g.msn.com/1HM205401/j>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> Have a look to our homepage at: http://www.consolut.net
> SAP on System i-unsubscribeZy...
>
> Your use of consolut is subject to
http://www.consolut.net


Durban Tours - Südafrika Safari

ROGBILLS - Synchronize billing plans   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 6996 Date: 20240302 Time: 103243     sap01-206 ( 3 ms )