RE: MULTIPROCESSOR settings on a multiple CPU server with
On HP, also watch your context switching in Unix, on the cpu's. My previous company used HP, and this was one of our major problems. -----Original Message----- From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] On Behalf Of Ford, Andrew G Sent: 14 December 2005 06:05 PM To: informix-list@iiug.org Subject: RE: MULTIPROCESSOR settings on a multiple CPU server with >MULTIPROCESSOR Specifies that you are running on a multiprocessor computer I was getting tripped up on: Running on a Multiprocessor Computer If you are running multiple CPU virtual processors on a multiprocessor computer, set the MULTIPROCESSOR parameter in the ONCONFIG file to 1. http://publib.boulder.ibm.com/infocenter/idshelp/v10/index.jsp I'm not running multiple CPU VPs, but I agree with you and Martin. Setting MULTIPROCESSOR to 1 is probably the right way to go. >The main problem is having more than 1 Virtual Shared Memory Segment. The real problem is that HP only has 2 or 3 registers to store the protection code for memory segments. The common solution is to keep the number of Virtual segments at 1 since you can't control the number of resident segments (1) and you usually only have 1 shared memory segment (unless you load balance the ipcshm poll threads across multiple CPUVPs.) >I though IDS merged the resident and 1st virtual segment under HPUX? It will, unless SINGLE_SEG_OFF is set to get around other HP/UX shared memory allocation limitations. Andrew Ford -----Original Message----- From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] On Behalf Of david@smooth1.co.uk Sent: Tuesday, December 13, 2005 10:24 PM To: informix-list@iiug.org Subject: Re: MULTIPROCESSOR settings on a multiple CPU server with 1. http://publib.boulder.ibm.com/infocenter/idshelp/v10/topic/com.ibm.admin doc/admin255.htm MULTIPROCESSOR Specifies that you are running on a multiprocessor computer so I would set it to 1. 2. Not sure so I would benckmark. I would probably go with more Poll threads. Which IDS version are we talking about? The main problem is having more than 1 Virtual Shared Memory Segment. Pity HP designed a crap processor that does not handle more than 3 shared memory segments. I though IDS merged the resident and 1st virtual segment under HPUX? Can IDS 10 merge shared memory message segments if you have more than one poll thread on a CPU VP? Another feature request? Are HP dropping PA-RISC in favour of Itanium? I though HP-UX 11.23 is Itanium only? David. sending to informix-list > The information on this e-mail including any attachments relates to the official business of DigiCare (Pty) Ltd. The information is confidential and legally privileged and is intended solely for the addressee. Access to this e-mail by anyone else is unauthorised and as such any disclosure, copying, distribution or any action taken or omitted in reliance on it is unlawful. Please notify the sender immediately if it has inadvertently reached you and do not read, disclose or use the content in any way. > No responsibility whatsoever is accepted by DigiCare (Pty) Ltd if the information is, for whatever reason, corrupted or does not reach its intended destination. The views expressed in this e-mail are the views of the individual sender and should in no way be construed as the views of DigiCare (Pty) Ltd, except where the sender has specifically stated them to be the views of DigiCare (Pty) Ltd. sending to informix-list sending to informix-list