Anyone who knows more, feel free to correct me if I'm wrong...
I've been testing various things on AIX 5.1 (not 5.2, yet...). With 5.1
came JFS2, and with that, the AIX buffer cache has changed a little.
"minperm" and "maxperm" relate mainly to JFS. The new parameter
"maxclient" relates to (I believe) NFS client cache, CDFS cached files,
and JFS2.
There is some relationship between "perm" and "client" pages such that
minperm <= maxclient <= maxperm
must hold true.
I'm yet to wrap my head around all of this, but I know that certain
combinations can be harmful... I've had response times on my test system
go up to around the two minute mark with minperm=1, maxclient=2,
maxperm=2
and strict_maxperm=1, although response times are fine with minperm=2,
maxclient=5, maxperm=8 and strict_maxperm=1.
On Saturday, Aug 2, 2003, at 01:38 Australia/Sydney, Wheelock, Michael
D wrote:
Hi,
I have AIX 5.2 ML01 with TSM 5.2.0.0 as the only application running
on the
system. In fact the only things I have installed here are TSM (server
and
client) and the management software for the FastT700 that it is using.
I am
having a problem with virtual memory. I have 8GB of ram. TSM's
buffpoolsize
is set to 4096000 (should be 4GB). When I boot the system, as much as
8GB
of the swap region is utilized. This slowly increases and finally
craters
the system.
I have looked at most of the articles on the list and they suggest as a
first step to dealing with virtual memory issues, setting Maxperm% to
40 (or
thereabouts) and minperm% to 10. When I execute this on AIX 5.2 I get
the
following:
usr/samples/kernel # ./vmtune -P 40
vmo: 1485-111 Invalid value 40 for tunable maxperm%
Value for tunable maxperm% must be greater than or equal to 80, value
of
tunable maxclient%
FYI, my DB and log segments are on filesystems rather than raw lv's.
Any
ideas?
Michael Wheelock
Integris Health of Oklahoma
This e-mail may contain identifiable health information that is
subject to protection
under state and federal law. This information is intended to be for
the use of the
individual named above. If you are not the intended recipient, be
aware that any
disclosure, copying, distribution or use of the contents of this
information is prohibited
and may be punishable by law. If you have received this electronic
transmission in
error, please notify us immediately by electronic mail (reply).
--
Paul Ripke
Unix/OpenVMS/TSM/DBA
101 reasons why you can't find your Sysadmin:
68: It's 9AM. He/She is not working that late.
-- Koos van den Hout
|
