Blogger Dave Dice takes issue with the view that initial thread placement onto resources is process agnostic. He describes an experiment that suggests it is not thread creation time, but rather process membership that determines thread placement. Dice continues, reporting that the Solaris team explained that the kernel is no longer using a simple maximum dispersal policy, but instead thread placement is now process membership-aware. Even with a policy that allows process-aware packing, however, placement reverts to spreading threads onto other nodes if a node becomes too saturated, he points out.
(Get More Information . .)