database.sarang.net
UserID
Passwd
Database
DBMS
MySQL
PostgreSQL
Firebird
Oracle
ㆍInformix
Sybase
MS-SQL
DB2
Cache
CUBRID
LDAP
ALTIBASE
Tibero
DB 문서들
스터디
Community
공지사항
자유게시판
구인|구직
DSN 갤러리
도움주신분들
Admin
운영게시판
최근게시물
Informix Q&A 1177 게시물 읽기
No. 1177
Re: Re: Check Point Duration이 너무 길면....
작성자
김재남
작성일
2001-12-11 20:11
조회수
7,051

관심을 가져 주셔서 감사드립니다.

필요하시다는 정보를 알려드리겠습니다.

1. onstat -p

Informix Dynamic Server Version 7.31.UC4 -- On-Line -- Up 8 days 11:10:30 --

-1668080 Kbytes

 

Profile

dskreads pagreads bufreads %cached dskwrits pagwrits bufwrits %cached

42094928 22024796 1945444226 97.84 23481142 22829239 360938164 93.49

 

isamtot open start read write rewrite delete commit rollbk

8734673 37167817 277463179 1289249652 136996407 13465472 41705966 11875575 2590

 

gp_read gp_write gp_rewrt gp_del gp_alloc gp_free gp_curs

0 0 0 0 0 0 0

 

ovlock ovuserthread ovbuff usercpu syscpu numckpts flushes

0 0 0 797073.85 123690.84 5713 15574

 

bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans

3801737 4718 511565332 1025 0 20053 8549565 34672004

 

ixda-RA idx-RA da-RA RA-pgsused lchwaits

9251537 1339689 10207850 20352716 14716776

 

 

 

2. onstat -F

 

Fg Writes LRU Writes Chunk Writes

0 9159293 12964600

 

address flusher state data

7d2c2500 0 I 0 = 0X0

7d2c29ec 1 I 0 = 0X0

7d2c2ed8 2 I 0 = 0X0

7d2c33c4 3 I 0 = 0X0

7d2c38b0 4 I 0 = 0X0

7d2c3d9c 5 I 0 = 0X0

7d2c4288 6 I 0 = 0X0

7d2c4774 7 I 0 = 0X0

states: Exit Idle Chunk Lru

 

 

 

 

3. onstat -l

Physical Logging

Buffer bufused bufsize numpages numwrits pages/io

P-2 0 128 9709534 112842 86.05

phybegin physize phypos phyused %used

10003f 250000 165028 0 0.00

 

Logical Logging

Buffer bufused bufsize numrecs numpages numwrits recs/pages pages/io

L-3 0 128 337659028 13572937 135704 24.9 100.0

Subsystem numrecs Log Space used

OLDRSAM 337659028 1581587664

 

address number flags uniqid begin size used %used

300126c8 1 U-B---- 1753 13d0cf 50000 50000 100.00

300126e4 2 U-B---- 1754 14941f 50000 50000 100.00

30012700 3 U-B---- 1755 15576f 50000 50000 100.00

3001271c 4 U-B---- 1756 161abf 50000 50000 100.00

30012738 5 U---C-L 1757 16de0f 50000 5704 11.41

30012754 6 U-B---- 1750 17a15f 50000 50000 100.00

30012770 7 U-B---- 1751 1864af 50000 50000 100.00

3001278c 8 U-B---- 1752 1927ff 50000 50000 100.00

 

 

 

4. informix 매개변수들(onstat -c)

# Physical Log Configuration

 

PHYSDBS rootdbs # Location (dbspace) of physical log

PHYSFILE 500000 # Physical log file size (Kbytes)

 

# Logical Log Configuration

 

LOGFILES 8 # Number of logical log files

LOGSIZE 100000 # Logical log size (Kbytes)

 

# Diagnostics

 

MSGPATH /informix/online.log # System message log file path

CONSOLE /dev/console # System console message path

ALARMPROGRAM /informix/etc/no_log.sh #log_full.sh # Alarm program path

SYSALARMPROGRAM /informix/etc/evidence.sh # System Alarm program path

TBLSPACE_STATS 1

 

# System Archive Tape Device

 

TAPEDEV /dev/rmt/1 # Tape device path

TAPEBLK 64 # Tape block size (Kbytes)

TAPESIZE 34500000 # Maximum amount of data to put on tape (Kbytes

)

 

#TAPEDEV /informix/BACKUP/archive # Tape device path

#TAPEBLK 64 # Tape block size (Kbytes)

#TAPESIZE 2000000 # Maximum amount of data to put on tape (Kbytes

)

#

# Log Archive Tape Device

# Log Archive Tape Device

 

LTAPEDEV /dev/null # Log tape device path

LTAPEBLK 64 # Log tape block size (Kbytes)

LTAPESIZE 34500000 # Max amount of data to put on log tape (Kbytes

)

 

# Optical

 

STAGEBLOB # Informix Dynamic Server/Optical staging area

 

# System Configuration

 

SERVERNUM 100 # Unique id corresponding to a Dynamic Server

instance

NETTYPE tlitcp,7,300,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 for multi-processor

NUMCPUVPS 7 # 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 0 # Affinity start processor

AFF_NPROCS 0 # Affinity number of processors

 

# Shared Memory Parameters

 

LOCKS 5000000 # Maximum number of locks

BUFFERS 600000 # Maximum number of shared buffers

NUMAIOVPS 2 # Number of IO vps

PHYSBUFF 256 # Physical log buffer size (Kbytes)

LOGBUFF 256 # Logical log buffer size (Kbytes)

LOGSMAX 20 # Maximum number of logical log files

CLEANERS 8 # Number of buffer cleaner processes

SHMBASE 0x20000000 # Shared memory base address

SHMVIRTSIZE 1000000 # initial virtual shared memory segment size

SHMADD 100000 # Size of new shared memory segments (Kbytes)

SHMTOTAL 3500000 # Total shared memory (Kbytes). 0=>unlimited

CKPTINTVL 90 # Check point interval (in sec)

LRUS 32 # 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 64 # Stack size (Kbytes)

 

# System Page Size

# BUFFSIZE - Dynamic Server no longer supports this configuration parameter.

# To determine the page size used by Dynamic Server 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 /informix/etc/dr.lostfound # DR lost+found file path

 

# CDR Variables

CDR_LOGBUFFERS 2048 # size of log reading buffer pool (Kbytes)

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 (Kb

ytes)

 

# Backup/Restore variables

BAR_ACT_LOG /tmp/bar_act.log

BAR_MAX_BACKUP 0

BAR_RETRY 1

BAR_NB_XPORT_COUNT 10

BAR_XFER_BUF_SIZE 31

BAR_BSALIB_PATH /usr/lib/ibsad001.so

 

# Informix Storage Manager variables

ISM_DATA_POOL ISMData # If the data pool name is changed, be sure to

# update $INFORMIXDIR/bin/onbar. Change to

# ism_catalog -create_bootstrap -pool <new name>

ISM_LOG_POOL ISMLogs

 

# Read Ahead Variables

RA_PAGES 1024 # Number of pages to attempt to read ahead

RA_THRESHOLD 1023 # Number of pages left before next group

 

# DBSPACETEMP:

# Dynamic Server equivalent of DBTEMP for SE. This is the list of dbspaces

# that the Dynamic Server SQL Engine will use to create temp tables etc.

# If specified it must be a colon separated list of dbspaces that exist

# when the Dynamic Server 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 tmpdbs # 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 Dynamic Server 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 Dynamic

Server)

DUMPCNT 1 # Number of shared memory or gcore dumps for

# a single user's session

 

FILLFACTOR 90 # Fill factor for building indexes

 

# method for Dynamic Server to use when determining current time

USEOSTIME 0 # 0: use internal time(fast), 1: get time from O

S(slow)

 

# Parallel Database Queries (pdq)

MAX_PDQPRIORITY 100 # Maximum allowed pdqpriority

DS_MAX_QUERIES 5 # Maximum number of decision support queries

DS_TOTAL_MEMORY 300000 # Decision support memory (Kbytes)

DS_MAX_SCANS 1048576 # Maximum number of decision support scans

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 0 # To hint the optimizer

 

ONDBSPACEDOWN 2 # Dbspace down option: 0 = CONTINUE, 1 = ABORT,

2 = WAIT

LBU_PRESERVE 1 # Preserve last log for log backup

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

 

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

OPT_GOAL -1

 

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

DIRECTIVES 1

 

# Status of restartable restore

RESTARTABLE_RESTORE off

 

 

 

-- 강병철 님이 쓰신 글:

>> 흠....이것만으로는 잘 모르겠구요...

>> 더 필요한 정보는...

>> onstat -p

>> onstat -F

>> onstat -l

>> onconfig 파일

>> 그리고....이 DB서버의 용도는 OLTP가 맞나요?

>> 아님 DSS인가요?

>> 것두 필요할것 같구....

>> 또 뭐가 있을까?????

>> 근데 사실 이경우는 계속 모니터링을 해야 하는데..

>> 단편적인 정보로는 약간 어려움이 있겠네요..

>> 필요하시면 인포믹스 서버튜닝가이드를 보내드리져..

>> 그럼...이만...

>>

>>

>> -- 김재남 님이 쓰신 글:

>> >> Log파일을 보면 check point duration이 너무 긴것 같습니다.

>> >> 도대체 왜 이런지 모르겠습니다. 몇가지 엔진 매개변수는 아래와 같습니다.

>> >> 먼저 하드웨어사항을 말씀드리겠습니다.

>> >>

>> >> 하드웨어사항.

>> >> 1. os : DG/UX (Data General Unix)

>> >> 2. cpu : 8개

>> >> 3. ram : 4기가바이트

>> >> 4. disk수 : 8개(개당 8기가. 개당 1기가씩 8개의 dbspace)

>> >>

>> >> 엔진매개변수

>> >> 1. BUFFERS 600000

>> >> 2. CLEANERS 8

>> >> 3. LRUS 32

>> >> 4. NUMCPUVPS 7

>> >> 5. LRU_MAX_DIRTY 1

>> >> 6. LRU_MIN_DIRTY 0

>> >>

>> >> 상태를 파악하는데 더 필요한 사항이 있다면 말씀해 주세요...

>> >> 꼭 해결하고 싶습니다.

>> >> 많은 분들의 관심바랍니다.

[Top]
No.
제목
작성자
작성일
조회
1179Client 버젼 질문
신호
2001-12-12
4423
1178Client 버젼 질문
신호
2001-12-12
4280
1181┕>Re: Client 버젼 질문
강병철
2001-12-12 17:34:41
4530
1189 ┕>Re: Re: Client 버젼 질문 [1]
신호
2001-12-18 00:32:01
4745
1172인포믹스 설치에 대해...
eroica
2001-12-11
4588
1171Check Point Duration이 너무 길면....
김재남
2001-12-11
4428
1173┕>Re: Check Point Duration이 너무 길면....
강병철
2001-12-11 14:59:07
4715
1177 ┕>Re: Re: Check Point Duration이 너무 길면....
김재남
2001-12-11 20:11:41
7051
1170Informix 어서 구해염.. ^^;
정규성
2001-12-11
5005
1175┕>Re: Informix 어서 구해염.. ^^;
강병철
2001-12-11 15:09:26
5581
1169도와주세요...
이재원
2001-12-11
5141
1174┕>Re: 도와주세요...
강병철
2001-12-11 15:02:58
5480
1164informix 설치(솔라리스용)
박성권
2001-12-10
5518
1165┕>http://tilldawn.co.kr 의 자료실에서 찾아보세요[냉무] ^^
딧세
2001-12-10 18:27:44
5152
Valid XHTML 1.0!
All about the DATABASE... Copyleft 1999-2024 DSN, All rights reserved.
작업시간: 0.020초, 이곳 서비스는
	PostgreSQL v16.2로 자료를 관리합니다