unprophete
Technical User
sometimes numperm grows up sometimes down but never cross minperm...
what should it mean from performance point of view?
minperm 20%
maxperm 80%
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
nmon statistics shows permanently numperm < minperm 1
- Thread starter unprophete
- Start date
- Status
sometimes numperm grows up sometimes down but never cross minperm...
what should it mean from performance point of view?
minperm 20%
maxperm 80%
minperm is a threshold, for that if numperm reaches or falls below would make LRUD steal memory from running processes which would be very bad. While numperm is above minperm, everything is ok and only cached files are cleared for memory needs.
To get not in such a bad situation, minperm is usually set very low.
Especially on DB servers it is set very low percentage like 5% for example while maxperm& and maxclient% is kept >80. Also lru_file_repage is set to 0.
The man page of vmo explains a lot about those parameters. For further in depth-information you might check out the peformance Red Books of IBM or Jaqui Lynch's perfomance guide (google it).
To make sure you might want to send the output of a
and also that of a
when having numperm < minperm.
Additional note:
Generally it is no problem to have low numperm, since it shows how much memory is actually used for caching files to prevent unnecessary, but as said in the previous posts, if there is not more memory left to satisfy minperm, then you will most probably have problems like a slow box.
If your available virtual memory is high enough and hopefully not just the part in paging space, then you will not have any problem, but anyway you can post the output I asked for up there.
laters
zaxxon
To get not in such a bad situation, minperm is usually set very low.
Especially on DB servers it is set very low percentage like 5% for example while maxperm& and maxclient% is kept >80. Also lru_file_repage is set to 0.
The man page of vmo explains a lot about those parameters. For further in depth-information you might check out the peformance Red Books of IBM or Jaqui Lynch's perfomance guide (google it).
To make sure you might want to send the output of a
Code:
vmstat -v
Code:
vmstat -w 1 10Additional note:
Generally it is no problem to have low numperm, since it shows how much memory is actually used for caching files to prevent unnecessary, but as said in the previous posts, if there is not more memory left to satisfy minperm, then you will most probably have problems like a slow box.
If your available virtual memory is high enough and hopefully not just the part in paging space, then you will not have any problem, but anyway you can post the output I asked for up there.
laters
zaxxon
- Status
