It's probably a good idea to do both. That way the zone has enough free memory for any additional software or non-oracle related software/services that are running. So if your database needs 8GBs of shared memory, you could set the max-shm-memory to 4GB and the max-shm-ids to 2. Then set the max memory for the zone to 8.5 or 9GB to give you 512MB or 1GB of memory for other stuff running in the zone. Definitely need to keep enough extra RAM laying around for logins and stuff.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Octave J. Orgeron Solaris Virtualization Architect and Consultant Web: http://unixconsole.blogspot.com E-Mail: unixcons...@yahoo.com *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* ----- Original Message ---- From: Mike DeMarco <mikej...@yahoo.com> To: opensolaris-discuss@opensolaris.org Sent: Tue, November 23, 2010 7:19:15 AM Subject: Re: [osol-discuss] Zones zone.max-shm-memory setting. zone.max-shm-memory defines the maximum size of a shared memory segment. So if it is set to 4Gig then the maximum shared memory segment will be 4 Gig. You can have up to zone.max-shm-ids segments set so this still can consume all of your memory.. If you want to limit the full amount of memory a zone can use you would set capped-memory, physical in your zone definition to the total amount of memory you want the zone to have. -- This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
