RE: Checkpoint is so sloooowww

Reduce LRU_MIN_DIRTY from 20 to 5, or even lower; reduce LRU_MAX_DIRTY from 30 to 10, or even lower. That means there is less writing to be done at the checkpoint because there are fewer dirty pages in memory. You could, in extremis, lower the minimum and maximum values to 0 and 1 respectively. The disadvantage of doing this is that there will be fewer occasions when more than one write occurs on a single dirty page, and there will be more write activity between checkpoints. On the other hand, the advantages of smoother (shorter) checkpoints probably outweigh the disadvantages. In general, the more main memory there is allocated to Online, the smaller the LRU_MIN_DIRTY and LRU_MAX_DIRTY parameters need to be. Yours, Jonathan Leffler (jleffler@visa.com) #include <bother.ms-exchange.h> ---------- From: andy@pneu.com[SMTP:andy@pneu.com] Sent: Thursday, April 09, 1998 6:59 AM To: informix-list@iiug.org Subject: Checkpoint is so sloooowww Hello !We use OnLine 5.08 on an digital-alpha server with 1 GB Ram and 4 CPU.- Buffers 10000, Locks 40000, Physbuf 256, unbuffered Logging. - 9 cleaners, 10 LRUS, clean beginns if 30% full, ends if 20% full. - checkpoint 300 sec. - root, log, phys and data in raw-devices on seperate Hdd's.Our problem is: DB needs about 10 sec for an complete chkpoint! While checkpoint is *running* all application-programms waiting forcompleting the checkpoint and the users can't work.How can i reduce this 10 secs for the checkpoints? Thanks in advice.Andreas Bettin -----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/ Now offering spam-free web-based newsreading