Ansicht
Dokumentation
03271 - *BASE Activity level?
Vendor Master (General Section) SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
*BASE Activity level?
Hi Andy,I hope I'm remebering things correctly but I think a high Active -> Wait
number is a good thing as long as you don't have jobs going ineligible
(sometimes a littlw wait to ineleigible is ok but no active to ineleigible).
We have 40 WP's and a QBASACTLVL of 140. I believe it was arrived at by
reducing it 10% at a time until some jobs began going ineligible. Our
performance hardly qualifies as honky-dory but I believe we are constrained
more by memory (4 Gig on an 8 processor machine is about 50% too low in my
estimation). Which brings us to the Database and Non-database faulting and
paging. I beleive they are more a measure of the amount of memory avialable
to the pool than the number of active threads allowed (of course lots of
active threads means less memory per thread so maybe there is some of both
there). In short, yes 500 sounds way too high for a 27 work process machine
unless you have a lot of other software running out of the base pool. If you
have enough of the performance tools that you get the Advisor option, take
it and see what it recommends (and take the recommendations with a grain of
salt).
Rick
-----Original Message-----
From: Squash [mailto:realsquashZy...]
Sent: Wednesday, September 26, 2001 3:50 PM
To: SAP AS/400 List
Subject: *BASE Activity level?
I'm having performance issues since my V4R5 upgrade and I noticed that my
*BASE pool activity
level is set to 500. SAP note 428855 says:
------------------------------
QBASACTLVL:
Activity Level of the *BASE Pool.Generally one or several SAP R/3 systems
are assigned to this
memory pool. The minimum size for this system value is:
QBASACTLVL > 1.2 * (number of work processes of all R/3 Systems)
A too great value causes a heavier paging.A too low value may result in
considerable performance
problems because jobs change into the Ineligible status.
------------------------------
Since I have 22 R/3 work processes that means it should be over about 27,
but 500 sounds very
excessive. I do not know what the value was for sure before the upgrade
(yeah yeah I should have
written it down), but I think it was 500 like it is now. Could this notes
actually mean the
number of total jobs running on the server?
I am having a problem where I get between 1000 and 2000 non-DB pages,
300-2000 Active -> Wait, and
around 100 non-DB faults in *BASE. This only happens after an R/3 job hangs
and I try to end it
by any means.
Please help! ARGH!
Thanks,
Andy Quaas
__________________________________________________
Do You consolut?
Get email alerts & NEW webcam video instant messaging with consolut Messenger.
http://im.consolut.net
Durban Tours - Südafrika Safari
BAL Application Log Documentation BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 3407 Date: 20240427 Time: 020858 sap01-206 ( 3 ms )
