When the freelist (the number of free pages in memory) falls below the
MINFREE parameter the VMM must free up memory untill MAXFREE is reached.
This message that you are getting just means that there have been page
faults and that memory load control is disabled. You can enable it by
running the command schedtune -h 6 (schedtune is available in /usr
/samples/kernel) You should not change the memory-load-control parameter
settings unless your workload is consistent and you believe the default
parameters are ill-suited to your workload.
..
## More info on Tuning VMM Memory Load Control ##
The VMM memory-load-control facility protects an overloaded system
from thrashing--a self-perpetuating paralysis in which the processes
in the system are spending all their time stealing memory frames from
one another and reading writing pages on the paging device.
Memory-Load-Control Tuning--Possible, but Usually Inadvisable.

"Bob" <bob@jriver.com> wrote in message
news:d4b639$2l0l$1@scream.jriver.com...
> I occasionally get this message in the PDT report (level 3)
> "There is evidence of memory contention, yet Memory Load Control is
> disabled"
>
> The system is 5.2 on a dual processor F80. It has 1.5G physical ram and
> 3G swap.
>
> It's running a bunch of instances of apache 1.3 mostly and the usual
> system stuff. NFS is turned off.
>
> Topas says that there is little swap in use:
>
> MEMORY
> Real,MB 1535
> % Comp 53.8
> % Noncomp 44.6
> % Client 45.2
>
> PAGING SPACE
> Size,MB 3072
> % Used 9.9
> % Free 90.0
>
> Is this important? Should I turn load control on? I looked in smit and
> couldn't find it!
>
> Bob