home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!rutgers!ub!niktow!pavlov
- From: pavlov@niktow.canisius.edu (Greg Pavlov)
- Newsgroups: comp.unix.ultrix
- Subject: Re: Some buffer cache questions
- Message-ID: <1926@niktow.canisius.edu>
- Date: 30 Dec 92 14:49:47 GMT
- References: <1992Dec23.022724.27844@pony.Ingres.COM> <1992Dec30.010315.8079@nntpd2.cxo.dec.com>
- Organization: Canisius College, Buffalo NY. 14208
- Lines: 30
-
- In article <1992Dec30.010315.8079@nntpd2.cxo.dec.com>, alan@nabeth.cxo.dec.com (Alan Rollow - Alan's Home for Wayward Tumbleweeds.) writes:
- >
- > >>[ I mention large buffer caches and delay_wbuffers ]
- > >
- > >So, what am I supposed to be watching the delay_wbuffers for?
- > >
- > This is a variable in param.c that has two values, zero and non-zero.
- > The default is zero. When set to zero the buffer cache code schedules
- > data writes as buffer are filled by the user........
- >
- > Related to this thread, Greg Pavlov at karloff.fstrf.org asked
- > what sort of trouble I had with large cache configurations. .....
- >
-
- Greg Pavlov asked the question because he has a DEC 5000/240 with the
- following:
-
- delay_wbuffers = 0
- total memory: 128 MB
- bufcache 60
-
- I don't know how close this may be to the original poster's request, but
- the above seems to work fine from a system point of view and the large
- set-aside for disk buffers seems to accomplish what we need for the
- particular application that this machine serves.
-
-
-
- greg pavlov
- pavlov@fstrf.org
-