Shared memory as default communic. protocol
We have Baan IVb2
Porting set : 6.1c.04.02
OS-release : AIX4.3.2.0
IDS Version: 7.31.UC5
Box:BULL RL
CPU: 4
Memory: 2.5 GB
I was told that in case of Host-Mode (1 box) we sould use shared memory
as default communication protocol.
I've tried but it didn't work.
What should I do ?
Is that the reason why run a script with 'dbaccess' and use baan_shm it
takes about 30 minutes (table with 20.000.000 records) and when I run
the same query in BaaN SQL it takes about 5 hours ?
Current configuration:
(SQlHOSTS)
baan onsoctcp atl baan m=1
baan_shm onipcshm atl baan
(ONCONFIG)
# System Configuration
SERVERNUM 0 # Unique id corresponding to
DBSERVERNAME baan # Name of default database server
DBSERVERALIASES baan_shm # List of alternate dbservernames
NETTYPE soctcp,3,100,CPU # Configure poll thread(s) for nettype
DEADLOCK_TIMEOUT 60 # Max time to wait of lock
RESIDENT 0 # Forced residency flag
MULTIPROCESSOR 1 # 0 for single-processor, 1 for multi-processor
NUMCPUVPS 3 # Number of user (cpu) vps
SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps
NOAGE 0 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors# Shared Memory Parameters
LOCKS 200000 # Maximum number of locks
BUFFERS 30000 # Maximum number of shared buffers
NUMAIOVPS 1 # Number of IO vps
PHYSBUFF 64 # Physical log buffer size (Kbytes)
LOGBUFF 64 # Logical log buffer size (Kbytes)LOGSMAX 64 # Maximum number of logical log files
CLEANERS 12 # Number of buffer cleaner processes
SHMBASE 0x30000000 # Shared memory base address
SHMVIRTSIZE 557056 # initial virtual shared memory segment
SHMADD 32768 # Size of new shared memory segments
SHMTOTAL 0 # Total shared memory (Kbytes).
CKPTINTVL 300 # Check point interval (in sec)
LRUS 32 # Number of LRU queues
LRU_MAX_DIRTY 90 # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 10 # LRU percent dirty end cleaning limit
LTXHWM 50 # Long transaction high water mark
LTXEHWM 60 # Long transaction high water mark
TXTIMEOUT 0x12c # Transaction timeout (in sec)
STACKSIZE 32 # Stack size (Kbytes)
Sent via Deja.com http://www.deja.com/
Before you buy.
1. I would recommend not using the same service name (baan) for shared
memory as well as onsoctcp. For shared memory, change the name to something
else, like baanshm.
2. What do you exactly mean by "it didn' t work"? Are you getting an error
message? Is it connecting but not making any difference?? Are you sure you
were using the correct INFORMIXSERVER (baan_shm) when connecting?
Oops, just noticed - you need to add another NETTYPE in your onconfig, for
example:
NETTYPE ipcshm,1,10,CPUand change the existing NETTYPE to use the NET class.
Only one protocol can run on the CPU vp. This is probably at least part of
the reason why your shared memory connections were not "working".
P.S. There is always some debate about which class is best (NET or CPU) for
which protocol. I typically use the above and have not had problems so
far... Informix perf. tuning manual states that you should put the protocol
that requires the best performance on the CPU vp, but I know several
installations (including mine) that put client/server protocols on NET and
shared memory protocol on CPU and performance is good...
3. Have you tuned the BUFFERS parameter on this system? It sounds very low
for a Baan system with potentially 300 users, especially when you consider
that you have 2.5GB of memory... What kind of read/write cache rates
(onstat -p) are you getting?
4. I do not know what kind of monster query that is but even 30 minutes
sounds very high to me (unless it is an overnight report or something...).
1, 2, 3 above should help on this...
Hal Maner
M Systems International, Inc.
www.msystemsintl.com
<meloi@my-deja.com> wrote in message news:8e70tr$636$1@nnrp1.deja.com...
> We have Baan IVb2
> Porting set : 6.1c.04.02
> OS-release : AIX4.3.2.0
> IDS Version: 7.31.UC5
> Box:BULL RL
> CPU: 4
> Memory: 2.5 GB
>
> I was told that in case of Host-Mode (1 box) we sould use shared memory
> as default communication protocol.
> I've tried but it didn't work.
> What should I do ?
>
> Is that the reason why run a script with 'dbaccess' and use baan_shm it
> takes about 30 minutes (table with 20.000.000 records) and when I run
> the same query in BaaN SQL it takes about 5 hours ?
>
> Current configuration:
> (SQlHOSTS)
> baan onsoctcp atl baan m=1
> baan_shm onipcshm atl baan>
> (ONCONFIG)
> # System Configuration
>
> SERVERNUM 0 # Unique id corresponding to
> DBSERVERNAME baan # Name of default database server
> DBSERVERALIASES baan_shm # List of alternate dbservernames
> NETTYPE soctcp,3,100,CPU # Configure poll thread(s) for nettype
> DEADLOCK_TIMEOUT 60 # Max time to wait of lock
> RESIDENT 0 # Forced residency flag
> MULTIPROCESSOR 1 # 0 for single-processor, 1 for multi-> processor
> NUMCPUVPS 3 # Number of user (cpu) vps
> SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps
> NOAGE 0 # Process aging
> AFF_SPROC 0 # Affinity start processor
> AFF_NPROCS 0 # Affinity number of processors> # Shared Memory Parameters
> LOCKS 200000 # Maximum number of locks
> BUFFERS 30000 # Maximum number of shared buffers
> NUMAIOVPS 1 # Number of IO vps
> PHYSBUFF 64 # Physical log buffer size (Kbytes)
> LOGBUFF 64 # Logical log buffer size (Kbytes)> LOGSMAX 64 # Maximum number of logical log files
> CLEANERS 12 # Number of buffer cleaner processes
> SHMBASE 0x30000000 # Shared memory base address
> SHMVIRTSIZE 557056 # initial virtual shared memory segment
> SHMADD 32768 # Size of new shared memory segments
> SHMTOTAL 0 # Total shared memory (Kbytes).
> CKPTINTVL 300 # Check point interval (in sec)
> LRUS 32 # Number of LRU queues
> LRU_MAX_DIRTY 90 # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY 10 # LRU percent dirty end cleaning limit
> LTXHWM 50 # Long transaction high water mark
> LTXEHWM 60 # Long transaction high water mark
> TXTIMEOUT 0x12c # Transaction timeout (in sec)
> STACKSIZE 32 # Stack size (Kbytes)>
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>ubject: Shared memory as default communic. protocol
>From: meloi@my-deja.com
>Date: 26.04.00 17:11 W. Europe Daylight Time
>Message-id: <8e70tr$636$1@nnrp1.deja.com>
>
>We have Baan IVb2
>Porting set : 6.1c.04.02
>OS-release : AIX4.3.2.0
>IDS Version: 7.31.UC5
>Box:BULL RL
>CPU: 4
>Memory: 2.5 GB
>
>I was told that in case of Host-Mode (1 box) we sould use shared memory
>as default communication protocol.
>I've tried but it didn´t work.
>What should I do ?
>
>Is that the reason why run a script with 'dbaccess' and use baan_shm it
>takes about 30 minutes (table with 20.000.000 records) and when I run
>the same query in BaaN SQL it takes about 5 hours ?
>
>Current configuration:
>(SQlHOSTS)
>baan onsoctcp atl baan m=1
>baan_shm onipcshm atl baan>
>(ONCONFIG)
># System Configuration
>
>SERVERNUM 0 # Unique id corresponding to
>DBSERVERNAME baan # Name of default database server
>DBSERVERALIASES baan_shm # List of alternate dbservernames
>NETTYPE soctcp,3,100,CPU # Configure poll thread(s) for nettype
>DEADLOCK_TIMEOUT 60 # Max time to wait of lock
>RESIDENT 0 # Forced residency flag
>MULTIPROCESSOR 1 # 0 for single-processor, 1 for multi->processor
>NUMCPUVPS 3 # Number of user (cpu) vps
>SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps
>NOAGE 0 # Process aging
>AFF_SPROC 0 # Affinity start processor
>AFF_NPROCS 0 # Affinity number of processors># Shared Memory Parameters
>LOCKS 200000 # Maximum number of locks
>BUFFERS 30000 # Maximum number of shared buffers
>NUMAIOVPS 1 # Number of IO vps
>PHYSBUFF 64 # Physical log buffer size (Kbytes)
>LOGBUFF 64 # Logical log buffer size (Kbytes)>LOGSMAX 64 # Maximum number of logical log files
>CLEANERS 12 # Number of buffer cleaner processes
>SHMBASE 0x30000000 # Shared memory base address
>SHMVIRTSIZE 557056 # initial virtual shared memory segment
>SHMADD 32768 # Size of new shared memory segments
>SHMTOTAL 0 # Total shared memory (Kbytes).
>CKPTINTVL 300 # Check point interval (in sec)
>LRUS 32 # Number of LRU queues
>LRU_MAX_DIRTY 90 # LRU percent dirty begin cleaning limit
>LRU_MIN_DIRTY 10 # LRU percent dirty end cleaning limit
>LTXHWM 50 # Long transaction high water mark
>LTXEHWM 60 # Long transaction high water mark
>TXTIMEOUT 0x12c # Transaction timeout (in sec)
>STACKSIZE 32 # Stack size (Kbytes)>
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.
>
>
>
>
>
>
you should have someone help you with the onconfig.
Nona