IDS Forum

RE: Performance issue after 732 to 94fc6 upgra....

Posted By: Simmons, Keith
Date: Tuesday, 13 June 2006, at 3:59 a.m.

In Response To: Re: Performance issue after 732 to 94fc6 upgrade p (Doug Fossmeyer)

Doug

See embedded comments below

Keith

-> -----Original Message-----
-> From: Doug Fossmeyer [mailto:DougF@SpokaneSchools.org]
-> Sent: Tuesday, June 13, 2006 1:04 AM
-> To: ids@iiug.org
-> Subject: Re: Performance issue after 732 to 94fc6 upgra.... [6934]
->
->
->
-> Part 2 of posting
->
-> onstat -c
->
-> IBM Informix Dynamic Server Version 9.40.FC6 -- On-Line --
-> Up 2 days 19:54:35
-> -- 2325280 Kbytes
->
-> Configuration File: /dbms/informix9/etc/onconfig.std
-> #************************************************************
-> **************
-> #
-> # INFORMIX SOFTWARE, INC.
-> #
-> # Title: onconfig.std
-> # Description: Informix Dynamic Server 9.4 Configuration Parameters
-> #************************************************************
-> **************
->
-> # Root Dbspace Configuration
->
-> ROOTNAME rootdbs # Root dbspace name
-> ROOTPATH /dbms/links/rootdbs9 # Path for device containing
-> root dbspace
-> ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes)
-> ROOTSIZE 30000 # 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 plogdbs94 # Location (dbspace) of physical log
-> PHYSFILE 127000 # Physical log file size (Kbytes)
->
-> # Logical Log Configuration
->
-> LOGFILES 101 # Number of logical log files
-> LOGSIZE 2000 # Logical log size (Kbytes)
->
-> # Diagnostics
->
-> MSGPATH /dbms/informix9/log/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 /dbms/informix9/etc/no_log.sh # Alarm program path
-> TBLSPACE_STATS 0 # Maintain tblspace statistics
->
-> # System Archive Tape Device
->
-> TAPEDEV /dev/null # Tape device path
-> TAPEBLK 256 # Tape block size (Kbytes)
-> TAPESIZE 70000000 # Maximum amount of data to put on tape (Kbytes)
->
-> # Log Archive Tape Device
->
-> LTAPEDEV /dr_data/log.bak # Log tape device path
-> LTAPEBLK 256 # Log tape block size (Kbytes)
-> LTAPESIZE 70000000 # Max amount of data to put on log tape (Kbytes)
->
-> # Optical
->
-> STAGEBLOB # Informix Dynamic Server staging area
->
-> # System Configuration
->
-> SERVERNUM 1 # Unique id corresponding to a OnLine instance
-> DBSERVERNAME online9 # Name of default database server
-> DBSERVERALIASES test9 # List of alternate dbservernames
-> NETTYPE ipcshm,2,100,CPU
-> NETTYPE soctcp,2,100,NET
-> #NETTYPE ipcshm,4,250,CPU
-> DEADLOCK_TIMEOUT 120 # Max time to wait of lock in distributed env.
-> RESIDENT 4294967295 # Forced residency flag (Yes = 1, No = 0)
Why this figure, alternatives are 1 or 0 ??

->
-> MULTIPROCESSOR 1 # 0 for single-processor, 1 for multi-processor
->
-> #turn this off if using VPCLASS
-> #NUMCPUVPS 3 # Number of user (cpu) vps
-> SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to one
-> #turn these 3 off if using above VPCLASS
-> #NOAGE 0 # Process aging
-> #AFF_SPROC 1 # Affinity start processor
-> #AFF_NPROCS 0 # Affinity number of processors
->
-> # Shared Memory Parameters
->
-> LOCKS 200000 # Maximum number of locks
-> BUFFERS 900000 # Maximum number of shared buffers
-> #turn this off if using VPCLASS
-> #NUMAIOVPS 3 # Number of IO vps
-> PHYSBUFF 320 # Physical log buffer size (Kbytes)
-> LOGBUFF 64 # Logical log buffer size (Kbytes)
-> CLEANERS 8 # Number of buffer cleaner processes
Should be the same as LRUS

-> SHMBASE 0x0 # Shared memory base address
-> SHMVIRTSIZE 327680
-> SHMADD 32768 # Size of new shared memory segments (Kbytes)
-> SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited
-> CKPTINTVL 300 # Check point interval (in sec)
-> LRUS 128 # Number of LRU queues
Perceived wisdom indicates 127 is a better figure

-> LRU_MAX_DIRTY 5.000000 # LRU percent dirty begin cleaning limit
-> LRU_MIN_DIRTY 2.000000 # LRU percent dirty end cleaning limit
-> TXTIMEOUT 0x12c # Transaction timeout (in sec)
-> STACKSIZE 64 # Stack size (Kbytes)
Try a larger figure here (256)

->
-> # 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.
->
-> DYNAMIC_LOGS 0
Not for performance, but set this to 1

-> LTXHWM 40
-> LTXEHWM 50
->
-> # 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
-> DRINTERVAL 30 # DR max time between DR buffer flushes (in sec)
-> DRTIMEOUT 30 # DR network timeout (in sec)
-> DRLOSTFOUND /usr/informix/etc/dr.lostfound # DR lost+found file path
->
-> # 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,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 /dbms/informix9/log/bar_act.log
->
-> # ON-Bar Log file - not in /tmp please
-> BAR_DEBUG_LOG /dbms/informix9/log/informix/bar_dbug.log
->
-> # ON-Bar Debug Log - not in /tmp please
-> BAR_MAX_BACKUP 0
-> BAR_RETRY 1
-> BAR_NB_XPORT_COUNT 10
-> 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
-> # was 16 and 8, using Belevue settings for test
-> RA_PAGES 32 # Number of pages to attempt to read ahead
-> RA_THRESHOLD 30 # Number of pages left before next group
From onstat -p your read ahead figures seem low, try setting THRESHOLD to 8

->
-> # 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 # Default temp dbspaces
-> DBSPACETEMP
-> tempdbs6:tempdbs7:tempdbs8:tempdbs9:tempdbs10:ifasdbs94temp
->
-> # 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 /tmp # Preserve diagnostics in this directory
-> DUMPSHMEM 0 # 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 10 # Maximum allowed pdqpriority
-> DS_MAX_QUERIES 2 # Maximum number of decision support queries
Try as high as 128

-> DS_TOTAL_MEMORY 17392 # Decision support memory (Kbytes)
If you have the physical memory try this up to 1024000

-> DS_MAX_SCANS 20 # Maximum number of decision support scans
Try much higher (1048576)

-> DATASKIP off
-> # 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 1 # 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 /dbms/informix9/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)
->
-> VPCLASS CPU,num=3,aff=1-3,noage
-> VPCLASS AIO,num=4,aff=0-3,noage
->

***********************************************************************************************
This message is sent in strict confidence for the addressee only. It may contain legally privileged information. The contents are not to be disclosed to anyone other than the addressee. Unauthorised recipients are requested to preserve this confidentiality and to advise the sender immediately of any error in transmission.

This footnote also confirms that this email message has been swept for the presence of computer viruses, however we cannot guarantee that this message is free from such problems.
***********************************************************************************************

Messages In This Thread

• Performance issue after 732 to 94fc6 upgrade
  Doug Fossmeyer -- Friday, 26 May 2006, at 1:20 p.m.
  • RE: Performance issue after 732 to 94fc6 upgrade
    Julio Gerardo Flores Olvera -- Friday, 26 May 2006, at 1:39 p.m.
  • RE: Performance issue after 732 to 94fc6 upgrade
    Marcus Haarmann -- Friday, 26 May 2006, at 1:45 p.m.
  • Re: Performance issue after 732 to 94fc6 upgrade
    ART KAGEL, BLOOMBERG/ 731 LEXIN -- Friday, 26 May 2006, at 1:50 p.m.
    • Re: Performance issue after 732 to 94fc6 upgrade
      Doug Fossmeyer -- Friday, 26 May 2006, at 5:42 p.m.
    • Re: Performance issue after 732 to 94fc6 upgrade
      Doug Fossmeyer -- Monday, 12 June 2006, at 2:55 p.m.
      • Re: Performance issue after 732 to 94fc6 upgrade
        Doug Fossmeyer -- Monday, 12 June 2006, at 3:01 p.m.
        • Re: Performance issue after 732 to 94fc6 upgrade
          ART KAGEL, BLOOMBERG/ 731 LEXIN -- Monday, 12 June 2006, at 4:43 p.m.
      • Re: Performance issue after 732 to 94fc6 upgrade
        Richard Snoke -- Monday, 12 June 2006, at 3:43 p.m.
    • Re: Performance issue after 732 to 94fc6 upgrade P
      Doug Fossmeyer -- Monday, 12 June 2006, at 8:02 p.m.
      • Re: Performance issue after 732 to 94fc6 upgra....
        ART KAGEL, BLOOMBERG/ 731 LEXIN -- Tuesday, 13 June 2006, at 10:08 a.m.
      • Re: Performance issue after 732 to 94fc6 upgra....
        Khaled Bentebal -- Tuesday, 13 June 2006, at 11:01 a.m.
    • Re: Performance issue after 732 to 94fc6 upgrade p
      Doug Fossmeyer -- Monday, 12 June 2006, at 8:03 p.m.
      • Re: Performance issue after 732 to 94fc6 upgra....
        ART KAGEL, BLOOMBERG/ 731 LEXIN -- Tuesday, 13 June 2006, at 9:54 a.m.
    • Re: Performance issue after 732 to 94fc6 upgrade p
      Doug Fossmeyer -- Monday, 12 June 2006, at 8:04 p.m.
      • RE: Performance issue after 732 to 94fc6 upgra....
        Marcus Haarmann -- Tuesday, 13 June 2006, at 1:44 a.m.
      • RE: Performance issue after 732 to 94fc6 upgra....
        Simmons, Keith -- Tuesday, 13 June 2006, at 3:59 a.m.
      • Re: Re: Performance issue after 732 to 94fc6 upgra
        Art S. Kagel -- Tuesday, 13 June 2006, at 9:49 a.m.
      • Re: Performance issue after 732 to 94fc6 upgra....
        Doug Fossmeyer -- Tuesday, 13 June 2006, at 1:00 p.m.
  • RE: Performance issue after 732 to 94fc6 upgrade
    Everett Mills -- Friday, 26 May 2006, at 3:23 p.m.
    • RE: Performance issue after 732 to 94fc6 upgrade
      Richard Snoke -- Friday, 26 May 2006, at 3:45 p.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.