In article <2a413b1f.0307161310.691bd4e0posting.google.com >, Tom wrote:Your testing is correct -- the understanding should be that pools are>I have some questions about Solaris 9 resource manager.
>1. I have the following pool configuration
>create pset netscape_pset (uint pset.max = 1)
>create pset default_pset (uint pset.min = 1; uint pset.max = 2)
>create pool default_pool (string pool.scheduler="FSS"; boolean
>pool.default = tr
>create pool netscape_pool (string pool.scheduler="IA")
>associate pool default_pool (pset default_pset)
>associate pool netscape_pool (pset netscape_pset)
>What I understand is all the porjects bind to default_pool can use
>upto two CPUs if it's busy and nobody using netscape project (which
>binds to netscape_pool). But I did the test, the result is: no matter
>project default is, and nobody using project netscape, project default
>only use ONE cpu. In this case, what's the use of uint pset.max?
allocated based on their configuration at pool reconfiguration time.
They are not scaled based upon workload today.
The point of pset.max (in combination with pool.importance) is to
determine allocation of resources at pool reconfiguration time.
When is pool reconfiguration time? Currently it is when you run
pooladm -c, perform DR, or reboot your system. Those are the
times when the number of CPUs in any pool could change.
If you're looking for scaling in relation to workload along with
proportional guarantees, you should be looking to the Fair Share
As long as your project(4) configuration allows both users "batch">2. If I run database and batch on one server, and I assign user
> project database, user "batch" to project batch. But my batch
> call user "database".
> so when I run batch under "newtask -v -p batch", every child
> mater it runs as user "batch" or user "databse", will run under
> "batch". Is it right? (Didn't get a chance to test it)
and "database" access to project "batch", that's correct. Project
credentials are inherited across fork(2).
Liane Praza (lianepeng.sun.com) -- Solaris Kernel Development