RE: Checkpoint

This is a multi-part message in MIME format. ------=_NextPart_000_0047_01C011DA.D9F92360 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit CheckpointJason The checkpoint duration is probably a result of the application. The checkpoint must wait until all processes get out of critical until it starts. There is some other work to do, but guessing at you system the actual time *doing* the checkpoint would be small. See the Admin Guide - Checkpoint - if you need more info. Some comments below. MW -----Original Message----- From: owner-informix-list@iiug.iiug.org [mailto:owner-informix-list@iiug.iiug.org]On Behalf Of JasonYLPang@pg.SLR.com Sent: Tuesday, August 29, 2000 3:12 PM To: informix-list@iiug.org Subject: Checkpoint Hi all, Why the checkpoint take longer time to complete? Is it something not right at onconfig file??? Server = SUN E6500 OS = Sun Solaris 2.6 Processors = 10 Memory = 4G Any help would be greatly appreciated. Thank you. Best Regards, Jason Informix Dynamic Server Version 7.30.UC5 -- On-Line -- Up 13:02:43 -- 1587776 Kbytes Message Log File: /usr/informix7/online.log 10:20:55 Logical Log 74491 Complete. 10:25:06 Checkpoint Completed: duration was 5 seconds. 10:30:06 Logical Log 74492 Complete. 10:30:06 Logical Log 74492 Complete. 10:30:11 Checkpoint Completed: duration was 5 seconds. 10:35:16 Checkpoint Completed: duration was 5 seconds. 10:40:21 Checkpoint Completed: duration was 5 seconds. 10:42:15 Logical Log 74493 Complete. 10:42:15 Logical Log 74493 Complete. 10:42:30 Logical Log 74494 Complete. 10:42:30 Logical Log 74494 Complete. 10:45:33 Checkpoint Completed: duration was 12 seconds. 10:51:46 Checkpoint Completed: duration was 73 seconds. 11:02:01 Checkpoint Completed: duration was 315 seconds. 11:02:31 Logical Log 74495 Complete. 11:02:31 Logical Log 74495 Complete. 11:06:46 Logical Log 74496 Complete. 11:06:46 Logical Log 74496 Complete. 11:07:03 Checkpoint Completed: duration was 2 seconds. 11:07:32 Checkpoint Completed: duration was 0 seconds. # Root Dbspace Configuration ROOTNAME rootdbs # Root dbspace name ROOTPATH /dev/rawlinks/rootdb01 # Path for device containing root dbspace ROOTOFFSET 0 # 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 256000 # Physical log file size (Kbytes) Move it elsewhere on another disk # Logical Log Configuration LOGFILES 156 # Number of logical log files LOGSIZE 20000 # Logical log size (Kbytes) Where are these? Not in rootdbs? # Diagnostics MSGPATH /usr/informix7/online.log # System message log file path CONSOLE /dev/console # System console message path ALARMPROGRAM /usr/informix7/etc/no_log.sh # Alarm program path # System Archive Tape Device TAPEDEV /dev/rmt/0h TAPEBLK 1024 # Tape block size (Kbytes) TAPESIZE 40000000 # Maximum amount of data to put on tape (Kbytes) # Log Archive Tape Device LTAPEDEV /dev/null # Tape device path LTAPEBLK 16 # Tape block size (Kbytes) LTAPESIZE 7000000 # Maximum amount of data to put on tape (Kbytes) # Optical STAGEBLOB # INFORMIX-OnLine/Optical staging area # System Configuration SERVERNUM 0 # Unique id corresponding to a OnLineinstance DBSERVERNAME infimacs2 # Name of default database server DBSERVERALIASES infimacs2_shm # List of alternate dbservernames NETTYPE ipcshm,9,100,CPU NETTYPE tlitcp,4,100,NET 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 formulti-processor NUMCPUVPS 9 # Number of user (cpu) vps #NUMCPUVPS 6 # Number of user (cpu) vps SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps toone NOAGE 1 # Process aging AFF_SPROC 0 # Affinity start processor AFF_NPROCS 9 # Affinity number of processors # Shared Memory Parameters LOCKS 4000000 # Increase by KH on 27 Jan 1999 BUFFERS 500000 # Increase by KH on 10 Jan 2000 NUMAIOVPS 6 # Number of IO vps PHYSBUFF 640 # Physical log buffer size (Kbytes) What is onstat -l ? LOGBUFF 640 # Logical log buffer size (Kbytes) waste - not using logs LOGSMAX 200 # Increased by Jason on 12 July 2000 CLEANERS 127 # CLEANERS changed by Kok Hong on 25th Aug2000 SHMBASE 0xa000000 # Shared memory base address SHMVIRTSIZE 327680 # Size of new shared memory segments (Kbytes) SHMADD 32768 # Size of new shared memory segments (Kbytes) What does onstat -g seg say with a large number of users on and active? SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited CKPTINTVL 300 # Check point interval (in sec) Could be longer. LRUS 127 # LRUS changed by Kok Hong on 25th Aug2000 LRU_MAX_DIRTY 2 # LRU percent dirty begin cleaning limit LRU_MIN_DIRTY 1 # LRU percent dirty end cleaning limit LTXHWM 50 # Long transaction high water markpercentage LTXEHWM 60 # Long transaction high water mark (exclusive) TXTIMEOUT 0x12c # Transaction timeout (in sec) STACKSIZE 32 # Stack size (Kbytes) # 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 workerthrea