Single vs multi cpu ids

Can you guys help me build a list of funtionality that changes or is not available when you have a single cpu vs a multi cpu environment? Please send me your thoughts so I can compile a document on this. Thanks, Kate (Sent by Blackberry)

Kate: Many of the PDQ features will look at the number of CPU VPs and only sp= awn a single thread per CPU VP. On a single CPU machine all latching is disabled. This saves calls mak= ing the processor sync. John = "Tomchik, Kate" = <Kate_Tomchik@hom = edepot.com> = To Sent by: ids@iiug.org = ids-bounces@iiug. = cc org = Subj= ect Single vs multi cpu ids [10760]= 12/14/2007 10:52 = AM = = = Please respond to = ids@iiug.org = = = Can you guys help me build a list of funtionality that changes or is no= t available when you have a single cpu vs a multi cpu environment? Please= send me your thoughts so I can compile a document on this. Thanks, Kate (Sent by Blackberry) ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =

Due to the expense of Informix licenseing I was forced to setup a small 300 million row DSS instance for one CPU. To get any meaningful performance out of this arragement I fragmented all the tables by expression an required the users to include the expression in there SQL's. This limited the breath of the searches. One thread for each table fragment. In my configuration the PDQ variables seem to apply some rules to memory management but their impact on overall performance is not clear due to the box "sucking wind" most of the time. HPUX 11i Inf 9.4 cheers