no checkpoint
Posted in 2003
Topics: Server Administration, Transactions, Locking & Isolation, Logging & Checkpoints, Networking & sqlhosts Configuration
Dear All,
I just want to know if I set the CKPTINTVL to 36000 which an hour, of
coz I have around 512 LRU to flush my buffer. Then what will be drawback for
my system.
Here is my onconfig
SERVERNUM 0 # Unique id corresponding to a DynamicServer i
stance
DBSERVERNAME ifmx_tcp # Name of default database server#DBSERVERALIASES ifmx # List of alternate dbservernames
#NETTYPE ipcshm,1,10,CPU # Configure poll thread(s) for nettype
#NETTYPE tlitcp,4,100,NET # Configure poll thread(s) for nettype
NETTYPE tlitcp,4,150,NET # Configure poll thread(s) for nettype
DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed
env.
RESIDENT 1 # Forced residency flag (Yes = 1, No = 0)
MULTIPROCESSOR 1 # 0 for single-processor, 1 formulti-processor
NUMCPUVPS 12 # 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 0 # Affinity number of processors
# Shared Memory Parameters
LOCKS 200000 # Maximum number of locks#BUFFERS 1536000 # Maximum number of shared buffers
BUFFERS 1126400 # Maximum number of shared buffers
NUMAIOVPS 2 # Number of IO vps
PHYSBUFF 32 # Physical log buffer size (Kbytes)
LOGBUFF 32 # Logical log buffer size (Kbytes)LOGSMAX 500 # Maximum number of logical log files
CLEANERS 128 # Number of buffer cleaner processes
SHMBASE 0xa000000 # Shared memory base address#SHMVIRTSIZE 2097152 # initial virtual shared memory segment
size
#SHMVIRTSIZE 3145000 # initial virtual shared memory segment
size
SHMVIRTSIZE 1048576 # initial virtual shared memory segment size
SHMADD 524288 # Size of new shared memory segments
(Kbytes)#SHMADD 131072 # Size of new shared memory segments
(Kbytes)
SHMTOTAL 0
CKPTINTVL 36000 # Check point interval (in sec)
LRUS 512 # Number of LRU queues
LRU_MAX_DIRTY 1 # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 0 # 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)
Thx
Franklin
"Franklin Tang" <franklin@macauslot.com> wrote in message news:badmbv$eqo1@ctmsun0.macau.ctm.net...
> Dear All,
> I just want to know if I set the CKPTINTVL to 36000 which an hour, of
36000 is ten hours, not 1 hr.
> LRUS 512 # Number of LRU queues
what version of informix you are using. IIRC, except for XPS, other versions
can't have more than 128 LRUs.
> LRU_MAX_DIRTY 1 # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY 0 # LRU percent dirty end cleaning limit
set it to 2 and 1.
To answer to your question, the longer checkpoint duration, the longer it
will take to recover after a crash.
rk-
Yes, I am using 64 bit Informix, The max LRU can be 512. So the only
drawback from long checkpoint interval is longer recovery?? that's it???
"Franklin Tang" <franklin@macauslot.com> '''g''l''s'D
:badmbv$eqo1@ctmsun0.macau.ctm.net...
> Dear All,
> I just want to know if I set the CKPTINTVL to 36000 which an hour, of
> coz I have around 512 LRU to flush my buffer. Then what will be drawback
for
> my system.
> Here is my onconfig
>
> SERVERNUM 0 # Unique id corresponding to a Dynamic> Server i
> stance
> DBSERVERNAME ifmx_tcp # Name of default database server> #DBSERVERALIASES ifmx # List of alternate dbservernames
> #NETTYPE ipcshm,1,10,CPU # Configure poll thread(s) for nettype
> #NETTYPE tlitcp,4,100,NET # Configure poll thread(s) for nettype
> NETTYPE tlitcp,4,150,NET # Configure poll thread(s) for nettype
> DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed
> env.
> RESIDENT 1 # Forced residency flag (Yes = 1, No = 0)
>
> MULTIPROCESSOR 1 # 0 for single-processor, 1 for> multi-processor
> NUMCPUVPS 12 # Number of user (cpu) vps
> SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to> one
>
> NOAGE 1 # 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 1536000 # Maximum number of shared buffers
> BUFFERS 1126400 # Maximum number of shared buffers
> NUMAIOVPS 2 # Number of IO vps
> PHYSBUFF 32 # Physical log buffer size (Kbytes)
> LOGBUFF 32 # Logical log buffer size (Kbytes)> LOGSMAX 500 # Maximum number of logical log files
> CLEANERS 128 # Number of buffer cleaner processes
> SHMBASE 0xa000000 # Shared memory base address> #SHMVIRTSIZE 2097152 # initial virtual shared memory segment
> size
> #SHMVIRTSIZE 3145000 # initial virtual shared memory segment
> size
> SHMVIRTSIZE 1048576 # initial virtual shared memory segmentsize
>
> SHMADD 524288 # Size of new shared memory segments
> (Kbytes)> #SHMADD 131072 # Size of new shared memory segments
> (Kbytes)
> SHMTOTAL 0
> CKPTINTVL 36000 # Check point interval (in sec)
> LRUS 512 # Number of LRU queues
> LRU_MAX_DIRTY 1 # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY 0 # LRU percent dirty end cleaning limit
> LTXHWM 50 # Long transaction high water mark> percentage
> LTXEHWM 60 # Long transaction high water mark
> (exclusive)
> TXTIMEOUT 0x12c # Transaction timeout (in sec)
> STACKSIZE 32 # Stack size (Kbytes)>
> Thx
> Franklin
>
>