dbTalk Databases Forums  

VPCLASS 'cpu' not enough physical procs for affinity

comp.databases.informix comp.databases.informix


Discuss VPCLASS 'cpu' not enough physical procs for affinity in the comp.databases.informix forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
sdhaya
 
Posts: n/a

Default VPCLASS 'cpu' not enough physical procs for affinity - 06-22-2007 , 03:21 AM






Hi,


I keep seeing this message "VPCLASS 'cpu' not enough physical procs
for affinity" in the "online.log". We are running our application in a
Sun V890 Server with 4CPU , 16GB RAM using "Informix Version
10.00.FC5" .

Please advise if there any issues with configuration file.

Find below the output of "uname -X", "onstat - " and the "onconfig"
file, part of the online.log file.


-bash-3.00$ uname -X
System = SunOS
Node = primesun-test
Release = 5.10
KernelID = Generic_118833-24
Machine = sun4u
BusType = <unknown>
Serial = <unknown>
Users = <unknown>
OEM# = 0
Origin# = 1
NumCPU = 4

-bash-3.00$ onstat -

IBM Informix Dynamic Server Version 10.00.FC5 -- On-Line -- Up
01:25:37 -- 8130560 Kbytes


#************************************************* *************************
#
# Licensed Material - Property Of IBM
#
# "Restricted Materials of IBM"
#
# IBM Informix Dynamic Server
# (c) Copyright IBM Corporation 1996, 2005 All rights reserved.
#
# Title: onconfig.std
# Description: IBM Informix Dynamic Server Configuration Parameters
#
#************************************************* *************************

# Root Dbspace Configuration

ROOTNAME rootdbs # Root dbspace name
ROOTPATH /dev/informix/rootdbs.d01 # Path for device containing root
dbspace
ROOTOFFSET 50 # Offset of root dbspace into device (Kbytes)
ROOTSIZE 1000000 # Size of root dbspace (Kbytes)

# Disk Mirroring Configuration Parameters

MIRROR 0 # Mirroring flag (Yes = 1, No = 0)
MIRRORPATH # Path for device containing mirrored root
MIRROROFFSET 0 # Offset into mirrored device (Kbytes)

# Physical Log Configuration

PHYSDBS rootdbs # Location (dbspace) of physical log
PHYSFILE 200000 # Physical log file size (Kbytes)

# Logical Log Configuration

LOGFILES 170 # Number of logical log files
LOGSIZE 2000 # Logical log size (Kbytes)
LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT)

# Tablespace Tablespace Configuration in Root Dbspace

TBLTBLFIRST 0 # First extent size (Kbytes) (0 = default)
TBLTBLNEXT 0 # Next extent size (Kbytes) (0 = default)

# Security
# DBCREATE_PERMISSION:
# By default any user can create a database. Uncomment
DBCREATE_PERMISSON to
# limit database creation to a specific user. Add a new
DBCREATE_PERMISSION
# line for each permitted user.

#DBCREATE_PERMISSION informix

# DB_LIBRARY_PATH:
# When loading a (C or C++) shared object (for a UDR or UDT), IDS
checks that
# the user-specified path starts with one of the directory prefixes
listed in
# the comma-separated list of prefixes in DB_LIBRARY_PATH. The string
# "$INFORMIXDIR/extend" must be included in DB_LIBRARY_PATH in order
for
# extensibility and IBM supplied blades to work correctly.

# DB_LIBRARY_PATH $INFORMIXDIR/extend

# IFX_EXTEND_ROLE:
# 0 (or off) => Disable use of EXTEND role to control who can register
# external routines.
# 1 (or on) => Enable use of EXTEND role to control who can register
# external routines. This is the default behaviour.
#
IFX_EXTEND_ROLE 1 # To control the usage of EXTEND role.

# Diagnostics

MSGPATH /export/home/informix/online.log # System message log file
path
CONSOLE /dev/console # System console message path

# To automatically backup logical logs, edit alarmprogram.sh and set
# BACKUPLOGS=Y
ALARMPROGRAM /export/home/informix/etc/alarmprogram.sh # Alarm
program path
ALRM_ALL_EVENTS 0 # Triggers ALARMPROGRAM for any event
occur
TBLSPACE_STATS 1 # Maintain tblspace statistics

# System Archive Tape Device

#TAPEDEV /dev/null # Tape device path
TAPEDEV /backup/Level0 # Log tape device path
TAPEBLK 256 # Tape block size (Kbytes)
TAPESIZE 60000000 # Maximum amount of data to put on tape (Kbytes)

# Log Archive Tape Device

LTAPEDEV /dev/null # Tape device path
#LTAPEDEV /export/home/informix/level0 # Log tape device path
LTAPEBLK 32 # Log tape block size (Kbytes)
LTAPESIZE 10240 # Max amount of data to put on log tape (Kbytes)

# Optical

STAGEBLOB # Informix Dynamic Server staging
area

# System Configuration

SERVERNUM 0 # Unique id corresponding to a OnLine instance
DBSERVERNAME primesun_test # Name of default database server
DBSERVERALIASES primesun_testtcp # List of alternate dbservernames
NETTYPE ipcshm,1,100,CPU # Configure poll thread(s) for nettype
NETTYPE tlitcp,1,200,NET # TCP/IP protocol for connection
DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed env.
RESIDENT 0 # Forced residency flag (Yes = 1, No = 0)

MULTIPROCESSOR 1 # 0 for single-processor, 1 for multi-
processor
NUMCPUVPS 2 # Number of user (cpu) vps
SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps
to one

NOAGE 0 # Process aging
AFF_SPROC 2 # Affinity start processor
AFF_NPROCS 4 # Affinity number of processors

# Shared Memory Parameters

LOCKS 800000 # Maximum number of locks
NUMAIOVPS 10 # Number of IO vps
PHYSBUFF 64 # Physical log buffer size (Kbytes)
LOGBUFF 64 # Logical log buffer size (Kbytes)
CLEANERS 10 # Number of buffer cleaner processes
SHMBASE 0x10A000000L # Shared memory base address
SHMVIRTSIZE 1500000 # initial virtual shared memory segment
size
SHMADD 100000 # Size of new shared memory segments (Kbytes)
EXTSHMADD 60000 # Size of new extension shared memory segments
(Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes).
0=>unlimited
CKPTINTVL 300 # Check point interval (in sec)
TXTIMEOUT 300 # Transaction timeout (in sec)
STACKSIZE 64 # Stack size (Kbytes)

# Dynamic Logging
# DYNAMIC_LOGS:
# 2 : server automatically add a new logical log when necessary.
(ON)
# 1 : notify DBA to add new logical logs when necessary. (ON)
# 0 : cannot add logical log on the fly. (OFF)
#
# When dynamic logging is on, we can have higher values for LTXHWM/
LTXEHWM,
# because the server can add new logical logs during long transaction
rollback.
# However, to limit the number of new logical logs being added, LTXHWM/
LTXEHWM
# can be set to smaller values.
#
# If dynamic logging is off, LTXHWM/LTXEHWM need to be set to smaller
values
# to avoid long transaction rollback hanging the server due to lack of
logical
# log space, i.e. 50/60 or lower.
#
# In case of system configured with CDR, the difference between LTXHWM
and
# LTXEHWM should be atleast 30% so that we could minimize log overrun
issue.

DYNAMIC_LOGS 2
LTXHWM 70
LTXEHWM 80

# System Page Size
# BUFFSIZE - OnLine no longer supports this configuration parameter.
# To determine the page size used by OnLine on your
platform
# see the last line of output from the command, 'onstat -
b'.


# Recovery Variables
# OFF_RECVRY_THREADS:
# Number of parallel worker threads during fast recovery or an offline
restore.
# ON_RECVRY_THREADS:
# Number of parallel worker threads during an online restore.

OFF_RECVRY_THREADS 10 # Default number of offline worker threads
ON_RECVRY_THREADS 1 # Default number of online worker threads

# Data Replication Variables
# DRAUTO: 0 manual, 1 retain type, 2 reverse type
DRAUTO 0 # DR automatic switchover
DRINTERVAL 30 # DR max time between DR buffer flushes (in sec)
DRTIMEOUT 30 # DR network timeout (in sec)
DRLOSTFOUND /export/home/informix/etc/dr.lostfound # DR lost+found
file path
DRIDXAUTO 0 # DR automatic index repair. 0=off, 1=on

# CDR Variables
CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional)
CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds)
CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR queue
(Kbytes)
CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0 none, 9 max)
CDR_SERIAL 0 # Serial Column Sequence
CDR_DBSPACE # dbspace for syscdr database
CDR_QHDR_DBSPACE # CDR queue dbspace (default same as catalog)
CDR_QDATA_SBSPACE # List of CDR queue smart blob spaces

# CDR_MAX_DYNAMIC_LOGS
# -1 => unlimited
# 0 => disable dynamic log addition
# >0 => limit the no. of dynamic log additions with the specified
value.
# Max dynamic log requests that CDR can make within one server
session.

CDR_MAX_DYNAMIC_LOGS 0 # Dynamic log addition disabled by default

# Backup/Restore variables
BAR_ACT_LOG /export/home/informix/bar_act.log # ON-Bar Log file -
not in /tmp please
BAR_DEBUG_LOG /export/home/informix/bar_dbug.log # ON-Bar Debug Log -
not in /tmp please
BAR_MAX_BACKUP 0
BAR_RETRY 1
BAR_NB_XPORT_COUNT 20
BAR_XFER_BUF_SIZE 31
RESTARTABLE_RESTORE ON
BAR_PROGRESS_FREQ 0

# Informix Storage Manager variables
ISM_DATA_POOL ISMData
ISM_LOG_POOL ISMLogs

# Read Ahead Variables
RA_PAGES 10 # Number of pages to attempt to read ahead
RA_THRESHOLD 6 # Number of pages left before next group

# DBSPACETEMP:
# OnLine equivalent of DBTEMP for SE. This is the list of dbspaces
# that the OnLine SQL Engine will use to create temp tables etc.
# If specified it must be a colon separated list of dbspaces that
exist
# when the OnLine system is brought online. If not specified, or if
# all dbspaces specified are invalid, various ad hoc queries will
create
# temporary files in /tmp instead.

DBSPACETEMP tempdbs01,tempdbs02,tempdbs03 # Default temp dbspaces

# DUMP*:
# The following parameters control the type of diagnostics information
which
# is preserved when an unanticipated error condition (assertion
failure) occurs
# during OnLine operations.
# For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No.

DUMPDIR /export/home/informix/tmp # Preserve diagnostics in this
directory
DUMPSHMEM 1 # Dump a copy of shared memory
DUMPGCORE 0 # Dump a core image using 'gcore'
DUMPCORE 0 # Dump a core image (Warning:this aborts OnLine)
DUMPCNT 1 # Number of shared memory or gcore dumps for
# a single user's session

FILLFACTOR 90 # Fill factor for building indexes

# method for OnLine to use when determining current time
USEOSTIME 0 # 0: use internal time(fast), 1: get time from OS(slow)

# Parallel Database Queries (pdq)
MAX_PDQPRIORITY 100 # Maximum allowed pdqpriority
DS_MAX_QUERIES # Maximum number of decision support queries
DS_TOTAL_MEMORY # Decision support memory (Kbytes)
DS_MAX_SCANS 1048576 # Maximum number of decision support scans
DS_NONPDQ_QUERY_MEM 128 # Non PDQ query memory (Kbytes)
DATASKIP off # List of dbspaces to skip

# OPTCOMPIND
# 0 => Nested loop joins will be preferred (where
# possible) over sortmerge joins and hash joins.
# 1 => If the transaction isolation mode is not
# "repeatable read", optimizer behaves as in (2)
# below. Otherwise it behaves as in (0) above.
# 2 => Use costs regardless of the transaction isolation
# mode. Nested loop joins are not necessarily
# preferred. Optimizer bases its decision purely
# on costs.
OPTCOMPIND 2 # To hint the optimizer

DIRECTIVES 1 # Optimizer DIRECTIVES ON (1/Default) or OFF (0)

ONDBSPACEDOWN 2 # Dbspace down option: 0 = CONTINUE, 1 = ABORT,
2 = WAIT
OPCACHEMAX 0 # Maximum optical cache size (Kbytes)

# HETERO_COMMIT (Gateway participation in distributed transactions)
# 1 => Heterogeneous Commit is enabled
# 0 (or any other value) => Heterogeneous Commit is disabled
HETERO_COMMIT 0

SBSPACENAME # Default smartblob space name - this is where
blobs
# go if no sbspace is specified when the smartblob is
# created. It is also used by some datablades as
# the location to put their smartblobs.
SYSSBSPACENAME # Default smartblob space for use by the
Informix
# Server. This is used primarily for Informix Server
# system statistics collection.

BLOCKTIMEOUT 3600 # Default timeout for system block
SYSALARMPROGRAM /export/home/informix/etc/evidence.sh # System
Alarm program path

# Optimization goal: -1 = ALL_ROWS(Default), 0 = FIRST_ROWS
OPT_GOAL -1

ALLOW_NEWLINE 0 # embedded newlines(Yes = 1, No = 0 or
anything but 1)


#Create Index Online Shared Memory usage limitation
ONLIDX_MAXMEM 5120 # Per pool per index (Kbytes)

#Timeout for client connection request
LISTEN_TIMEOUT 10 # Timeout (in Seconds)

#Following are the deprecated configuration parameters, instead of
these
#use BUFFERPOOL configuration parameter
#BUFFERS, LRUS, LRU_MIN_DIRTY, LRU_MAX_DIRTY

IFX_FOLDVIEW 0 # fold multiple tables or union all view with
ansi joins
#
# The following are default settings for enabling Java in the
database.
# Replace all occurrences of /usr/informix with the value of
$INFORMIXDIR.

#VPCLASS jvp,num=1 # Number of JVPs to start with

JVPJAVAHOME /usr/informix/extend/krakatoa/jre/ # JRE
installation root directory
JVPHOME /usr/informix/extend/krakatoa # Krakatoa installation
directory

JVPPROPFILE /usr/informix/extend/krakatoa/.jvpprops # JVP property
file
JVPLOGFILE /usr/informix/jvp.log # JVP log file.

JDKVERSION 1.4 # JDK version supported by this server

# The path to the JRE libraries relative to JVPJAVAHOME
JVPJAVALIB /lib/sparcv9/

# The JRE libraries to use for the Java VM

JVPJAVAVM hpi:server:verify:java:net:zip:jpeg

# use JVPARGS to change Java VM configuration
#To display jni call
#JVPARGS -verbose:jni

# Classpath to use upon Java VM start-up (use _g version for
debugging)

# JVPCLASSPATH /usr/informix/extend/krakatoa/krakatoa_g.jar:/usr/
informix/extend/krakatoa/jdbc_g.jar
JVPCLASSPATH /usr/informix/extend/krakatoa/krakatoa.jar:/usr/informix/
extend/krakatoa/jdbc.jar

# The following parameters are related to the buffer pool
BUFFERPOOL
size=2K,buffers=3000000,lrus=128,lru_min_dirty=10. 000000,lru_max_dirty=20.000000



Fri Jun 22 08:03:14 2007

08:03:14 Event alarms enabled. ALARMPROG = '/export/home/informix/
etc/alarmprogram.sh'
08:03:14 Booting Language <c> from module <>
08:03:14 Loading Module <CNULL>
08:03:14 Booting Language <builtin> from module <>
08:03:14 Loading Module <BUILTINNULL>
08:03:19 DR: DRAUTO is 0 (Off)
08:03:19 Requested shared memory segment size rounded from 1080KB to
2048KB
08:03:20 IBM Informix Dynamic Server Version 10.00.FC5 Software
Serial Number AAA#B000000
08:03:22 IBM Informix Dynamic Server Initialized -- Shared Memory
Initialized.

08:03:22 Physical Recovery Started at Page (1:47829).
08:03:22 Physical Recovery Complete: 0 Pages Examined, 0 Pages
Restored.
08:03:23 Logical Recovery Started.
08:03:23 10 recovery worker threads will be started.
08:03:26 Logical Recovery has reached the transaction cleanup phase.
08:03:26 Logical Recovery Complete.
0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks

08:03:28 Dataskip is now OFF for all dbspaces
08:03:28 Checkpoint Completed: duration was 0 seconds.
08:03:28 Checkpoint loguniq 317, logpos 0x3704018, timestamp:
0x8698c72b

08:03:28 Maximum server connections 0
08:03:28 On-Line Mode
08:03:28 VPCLASS 'cpu' not enough physical procs for affinity
08:04:15 Booting Language <spl> from module <>
08:04:15 Loading Module <SPLNULL>
08:04:26 Logical Log 317 Complete, timestamp: 0x869b761f.
08:04:56 Logical Log 318 Complete, timestamp: 0x86a13758.
08:06:48 Unloading Module <SPLNULL>
08:07:04 Checkpoint Completed: duration was 3 seconds.
08:07:04 Checkpoint loguniq 319, logpos 0x59ad018, timestamp:
0x86a67a88

08:07:04 Maximum server connections 2
08:07:05 IBM Informix Dynamic Server Stopped.

08:07:12 IBM Informix Dynamic Server Started.
08:07:12 Requested shared memory segment size rounded from 1500000KB
to 1500160KB


Reply With Quote
  #2  
Old   
Superboer
 
Posts: n/a

Default Re: VPCLASS 'cpu' not enough physical procs for affinity - 06-22-2007 , 03:26 AM






you could try:

AFF_SPROC 0 # Affinity start processor

Superboer.


Reply With Quote
  #3  
Old   
sdhaya
 
Posts: n/a

Default Re: VPCLASS 'cpu' not enough physical procs for affinity - 06-22-2007 , 05:35 AM



On Jun 22, 11:26 am, Superboer <superbo... (AT) t-online (DOT) de> wrote:
Quote:
you could try:

AFF_SPROC 0 # Affinity start processor

Superboer.
Will try and let you know...

Thanks

Dhaya



Reply With Quote
  #4  
Old   
Art S. Kagel
 
Posts: n/a

Default Re: VPCLASS 'cpu' not enough physical procs for affinity - 06-22-2007 , 07:24 AM



On Jun 22, 4:21 am, sdhaya <dhaya.sni... (AT) gmail (DOT) com> wrote:
Quote:
Hi,

I keep seeing this message "VPCLASS 'cpu' not enough physical procs
for affinity" in the "online.log". We are running our application in a
Sun V890 Server with 4CPU , 16GB RAM using "Informix Version
10.00.FC5" .

Please advise if there any issues with configuration file.

Find below the output of "uname -X", "onstat - " and the "onconfig"
file, part of the online.log file.
Sun doesn't number it's CPUs sequentially and the CPU number for the
first CPU may or may not be 0 or 1. There is a Sun utility that will
give you the CPU #s of your CPUs (depends on what slots the CPU cards
are in). Then you can select one of those for AFF_SPROC. Once it
gets the number of the first CPU, IDS can determine the others to
use. Probably on your system there is no CPU #2.

Art S. Kagel




Reply With Quote
  #5  
Old   
TBP (The Big Potato)
 
Posts: n/a

Default Re: VPCLASS 'cpu' not enough physical procs for affinity - 06-22-2007 , 07:28 AM



Art S. Kagel wrote:
Quote:
On Jun 22, 4:21 am, sdhaya <dhaya.sni... (AT) gmail (DOT) com> wrote:

Hi,

I keep seeing this message "VPCLASS 'cpu' not enough physical procs
for affinity" in the "online.log". We are running our application in a
Sun V890 Server with 4CPU , 16GB RAM using "Informix Version
10.00.FC5" .

Please advise if there any issues with configuration file.

Find below the output of "uname -X", "onstat - " and the "onconfig"
file, part of the online.log file.


Sun doesn't number it's CPUs sequentially and the CPU number for the
first CPU may or may not be 0 or 1. There is a Sun utility that will
give you the CPU #s of your CPUs (depends on what slots the CPU cards
are in). Then you can select one of those for AFF_SPROC. Once it
gets the number of the first CPU, IDS can determine the others to
use. Probably on your system there is no CPU #2.

Art S. Kagel


psrinfo


Reply With Quote
  #6  
Old   
sdhaya
 
Posts: n/a

Default Re: VPCLASS 'cpu' not enough physical procs for affinity - 06-22-2007 , 06:14 PM



The following is the output of psrinfo in our Sun V890 ...

# psrinfo
0 on-line since 06/16/2007 15:09:23
2 on-line since 06/16/2007 15:09:19
16 on-line since 06/16/2007 15:09:23
18 on-line since 06/16/2007 15:09:23

Please advise the value..

Dhaya


On Jun 22, 3:28 pm, "TBP (The Big Potato)" <T... (AT) NotHere (DOT) Co.Uk> wrote:
Quote:
Art S. Kagel wrote:
On Jun 22, 4:21 am, sdhaya <dhaya.sni... (AT) gmail (DOT) com> wrote:

Hi,

I keep seeing this message "VPCLASS 'cpu' not enough physical procs
for affinity" in the "online.log". We are running our application in a
Sun V890 Server with 4CPU , 16GB RAM using "Informix Version
10.00.FC5" .

Please advise if there any issues with configuration file.

Find below the output of "uname -X", "onstat - " and the "onconfig"
file, part of the online.log file.

Sun doesn't number it's CPUs sequentially and the CPU number for the
first CPU may or may not be 0 or 1. There is a Sun utility that will
give you the CPU #s of your CPUs (depends on what slots the CPU cards
are in). Then you can select one of those for AFF_SPROC. Once it
gets the number of the first CPU, IDS can determine the others to
use. Probably on your system there is no CPU #2.

Art S. Kagel

psrinfo- Hide quoted text -

- Show quoted text -



Reply With Quote
  #7  
Old   
Frank Langelage
 
Posts: n/a

Default Re: VPCLASS 'cpu' not enough physical procs for affinity - 06-23-2007 , 04:54 AM



sdhaya wrote:
Quote:
The following is the output of psrinfo in our Sun V890 ...

# psrinfo
0 on-line since 06/16/2007 15:09:23
2 on-line since 06/16/2007 15:09:19
16 on-line since 06/16/2007 15:09:23
18 on-line since 06/16/2007 15:09:23

Please advise the value..

Dhaya


On Jun 22, 3:28 pm, "TBP (The Big Potato)" <T... (AT) NotHere (DOT) Co.Uk> wrote:
Art S. Kagel wrote:
On Jun 22, 4:21 am, sdhaya <dhaya.sni... (AT) gmail (DOT) com> wrote:
Hi,
I keep seeing this message "VPCLASS 'cpu' not enough physical procs
for affinity" in the "online.log". We are running our application in a
Sun V890 Server with 4CPU , 16GB RAM using "Informix Version
10.00.FC5" .
Please advise if there any issues with configuration file.
Find below the output of "uname -X", "onstat - " and the "onconfig"
file, part of the online.log file.
Sun doesn't number it's CPUs sequentially and the CPU number for the
first CPU may or may not be 0 or 1. There is a Sun utility that will
give you the CPU #s of your CPUs (depends on what slots the CPU cards
are in). Then you can select one of those for AFF_SPROC. Once it
gets the number of the first CPU, IDS can determine the others to
use. Probably on your system there is no CPU #2.
Art S. Kagel
psrinfo- Hide quoted text -

- Show quoted text -


If you stay with NUMCPUVPS set to 2, set AFF_SPROC to 16.
As long as you don't configure more NUMCPUVPS than physical CPUs, set
AFF_NPROCS to the same value as NUMCPUVPS.
With NUMCPUVPS 3 you would set AFF_SPROC to 2.
CPU 0 should be the last you use to bind processes to.


Reply With Quote
  #8  
Old   
sdhaya
 
Posts: n/a

Default Re: VPCLASS 'cpu' not enough physical procs for affinity - 06-24-2007 , 02:04 PM



On Jun 23, 12:54 pm, Frank Langelage <f... (AT) lafr (DOT) de> wrote:
Quote:
sdhaya wrote:
The following is the output of psrinfo in our Sun V890 ...

# psrinfo
0 on-line since 06/16/2007 15:09:23
2 on-line since 06/16/2007 15:09:19
16 on-line since 06/16/2007 15:09:23
18 on-line since 06/16/2007 15:09:23

Please advise the value..

Dhaya

On Jun 22, 3:28 pm, "TBP (The Big Potato)" <T... (AT) NotHere (DOT) Co.Uk> wrote:
Art S. Kagel wrote:
On Jun 22, 4:21 am, sdhaya <dhaya.sni... (AT) gmail (DOT) com> wrote:
Hi,
I keep seeing this message "VPCLASS 'cpu' not enough physical procs
for affinity" in the "online.log". We are running our application in a
Sun V890 Server with 4CPU , 16GB RAM using "Informix Version
10.00.FC5" .
Please advise if there any issues with configuration file.
Find below the output of "uname -X", "onstat - " and the "onconfig"
file, part of the online.log file.
Sun doesn't number it's CPUs sequentially and the CPU number for the
first CPU may or may not be 0 or 1. There is a Sun utility that will
give you the CPU #s of your CPUs (depends on what slots the CPU cards
are in). Then you can select one of those for AFF_SPROC. Once it
gets the number of the first CPU, IDS can determine the others to
use. Probably on your system there is no CPU #2.
Art S. Kagel
psrinfo- Hide quoted text -

- Show quoted text -

If you stay with NUMCPUVPS set to 2, set AFF_SPROC to 16.
As long as you don't configure more NUMCPUVPS than physical CPUs, set
AFF_NPROCS to the same value as NUMCPUVPS.
With NUMCPUVPS 3 you would set AFF_SPROC to 2.
CPU 0 should be the last you use to bind processes to.- Hide quoted text -

- Show quoted text -
Thanks for all the advice..

Dhaya



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.