Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Bill Hamilton — — source: Usenet: comp.databases.informix
After a checkpoint, how many "buffers not flushed" is considered acceptable?
Let's say the typical check point (every 15 minutes) looks like this:
10:30:40 Maximum server connections 296
10:45:40 Fuzzy Checkpoint Completed: duration was 0 seconds, 179 buffers
not flushed,
timestamp: 1279827764.
10:45:40 Checkpoint loguniq 423, logpos 0x3228a4, timestamp: 1279827764
The number not flushed ranges from 130 to 190.
These are some settings:
BUFFERS 60000 # Maximum number of shared buffers
CKPTINTVL 900 # Check point interval (in sec)
LRUS 128 # Number of LRU queues
LRU_MAX_DIRTY 10 # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 2 # LRU percent dirty end cleaning limitonstat -p (after about 3 hours use after a clear) looks like this
IBM Informix Dynamic Server Version 9.40.TC2 -- On-Line -- Up 68 days
22:10:04 -- 359360 Kbytes
Profile
dskreads pagreads bufreads %cached dskwrits pagwrits bufwrits %cached
18474 115424 22278735 99.92 8587 12262 79170 89.15
isamtot open start read write rewrite delete commit
rollbk
32781258 1951207 2053832 16244836 20829 11720 13356 5659 6
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 341.95 101.13 53 522
bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans
86 0 24668711 0 0 3 429 8190
ixda-RA idx-RA da-RA RA-pgsused lchwaits
0 0 0 0 93
sending to informix-list
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.