ovbuff vs. fgwrites question

This may be a stupid question but you know the old saying..... I noticed an increase in 'ovbuff' on the onstat -p. This is a very small database running on NT and so I increased my buffers. I then realized that this number is the same as my 'fgwrites'. Is this one and the same and if so why? Version 7.30.TC3 on NT. Thank alot folks, Bobby

In article <382C304D.90240C61@texas.net>, Bobby Medus <jeepin@eatmydirt.com> wrote: > This may be a stupid question but you know the old saying..... > > I noticed an increase in 'ovbuff' on the onstat -p. This is a very > small database running on NT and so I increased my buffers. I then > realized that this number is the same as my 'fgwrites'. Is this one and > the same and if so why? > > Version 7.30.TC3 on NT. > > Thank alot folks, > > Bobby > > If I remember correctly, ovbuff is buffer overflows. fgwrites are fore-ground writes and are commonly referred to as 'evil spawn of satan' :). The numbers are not the same thing, but one response to a buffer overflow is to do a fore-ground write. I would think that increasing your buffers is a good place to start in correcting the problem. -- # unrm / ksh: unrm: not found # man cpio Sent via Deja.com http://www.deja.com/ Before you buy.

Bobby Medus <jeepin@eatmydirt.com> wrote in message news:382C304D.90240C61@texas.net... > This may be a stupid question but you know the old saying..... > > I noticed an increase in 'ovbuff' on the onstat -p. This is a very > small database running on NT and so I increased my buffers. I then > realized that this number is the same as my 'fgwrites'. Is this one and > the same and if so why? Number in 'ovbuff' can be increased each time Informix tries to locate free buffer in FLRU queue and can't found buffer. As far as FLRU queue selection is based on the hash function (as far as I remember), it doesn't mean, that Informix have no free buffers at all. On the other hand, foreground write , means that sqlexec thread can't locate free buffer in the buffer pool. This means that buffer pool is empty and that all buffers are dirty buffers or locked buffers. In this situation sqlexec flushes dirty buffer on disk and locks emptied buffer. ------------------------------------------------- With best regards, Yuri Dovgart SAP R/3, Informix technical consultant, Informix Certified Professional, Senior System Consultant System Architecture and High Availability Systems, 'Telecominvest' company Email y_dovgart@tci.ukrtel.net ICQ 39284285 > > Version 7.30.TC3 on NT. > > Thank alot folks, > > Bobby >