shared memory question
Posted in 1999
Topics: Server Administration, Platform-Specific Issues
I have a configuration question on the onconfig file. I'm wanting to change (increase) the number of BUFFERS and SHMVIRTSIZE on the instance I'm running, but I'm wondering if I should be concerned with the Unix memory configuration before doing so. Here are my Solaris 2.6 memory parameters if it helps: set shmsys:shminfo_shmmax=268435456 set shmsys:shminfo_shmseg=200 set shmsys:shminfo_shmmin=100 set shmsys:shminfo_shmmni=200 set semsys:seminfo_semmap=100 set semsys:seminfo_semmni=4096 set semsys:seminfo_semmns=4096 set semsys:seminfo_semmnu=4096 set semsys:seminfo_semmsl=512 set semsys:seminfo_semume=100 -- Phillip Tien We tend to scoff at the beliefs of the ancients. But we can't scoff at them personally, to their faces, and this is what annoys me.
Phillip Tien wrote: > > I have a configuration question on the onconfig file. I'm wanting to > change (increase) the number of BUFFERS and SHMVIRTSIZE on the instance > I'm running, but I'm wondering if I should be concerned with the Unix > memory configuration before doing so. Here are my Solaris 2.6 memory > parameters if it helps: > set shmsys:shminfo_shmmax=268435456 This says the maximum size of any single shared memory segment is ~256MB Informix will allocate multiple segments if it has to, on Sun this is not a problem though startup is faster with a single segment. > set shmsys:shminfo_shmseg=200 Allows up to 200 shared memory segments. You will need one or more for the resident segment, as above, plus the initial virtual segment, plus one segment for each listener configured in the NETTYPE ONCONFIG parameter (second field), plus allowance for additional virtual segments as needed and any other shared memory you other applications will use. > set semsys:seminfo_semmap=100 Allow up to 100 semaphores per semaphore group. Informix uses 25 per group. > set semsys:seminfo_semmni=4096 Permit up to 4096 semaphore groups. Informix will need 1 group for each 25 user conections configured in all NETTYPE parameters (3rd field). These are the most relevant kernel parameters to look at, other snipped. Art S. Kagel
In article <7jls9m$56f$1@news.xmission.com>, Phillip Tien <phillip.tien@wholefoods.com> writes > >I have a configuration question on the onconfig file. I'm wanting to >change (increase) the number of BUFFERS and SHMVIRTSIZE on the instance >I'm running, but I'm wondering if I should be concerned with the Unix >memory configuration before doing so. Here are my Solaris 2.6 memory >parameters if it helps: > >set shmsys:shminfo_shmmax=268435456 >set shmsys:shminfo_shmseg=200 >set shmsys:shminfo_shmmin=100 PS as an aside, set shmmin to 1. It must be less than 28 or you get errors from powerd (power management??) when you reboot saying that it cannot allocate shared memory.. >set shmsys:shminfo_shmmni=200 >set semsys:seminfo_semmap=100 >set semsys:seminfo_semmni=4096 >set semsys:seminfo_semmns=4096 >set semsys:seminfo_semmnu=4096 >set semsys:seminfo_semmsl=512 >set semsys:seminfo_semume=100 > >-- >Phillip Tien > >We tend to scoff at the beliefs of the ancients. But we can't scoff at >them personally, to their faces, and this is what annoys me. > > -- David Williams