You can control resident set size (RSS) usage of a zone by setting the capped-memory resource when you configure the zone. For more information, see Physical Memory Control and the capped-memory Resource in Introduction to Oracle Solaris Zones . To use the capped-memory resource, the resource-cap package must be installed in the global zone. You can run rcapd within a zone, including the global zone, to enforce memory caps on projects in that zone.
You can set a temporary cap for the maximum amount of memory that can be consumed by a specified zone, until the next reboot. See How to Specify a Temporary Resource Cap for a Zone.
If you are using rcapd on a zone to regulate physical memory consumption by processes running in projects that have resource caps defined, you must configure the daemon in those zones.
When choosing memory caps for applications in different zones, you generally do not have to consider that the applications reside in different zones. The exception is per-zone services. Per-zone services consume memory. This memory consumption must be considered when determining the amount of physical memory for a system, as well as memory caps.