home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!munnari.oz.au!metro!grivel!alsvid.une.edu.au!mark
- From: mark@alsvid.une.edu.au (Mark Garrett Internet: mark@arvak.une.edu.au Phone: +61 66 20 3859)
- Newsgroups: comp.unix.ultrix
- Subject: Re: Some buffer cache questions
- Message-ID: <C0Dq1o.1rA@alsvid.une.edu.au>
- Date: 5 Jan 93 11:46:36 GMT
- References: <1992Dec29.224612.14664@pony.Ingres.COM>
- Organization: University of New England - Northern Rivers (Lismore)
- Lines: 21
-
- From article <1992Dec29.224612.14664@pony.Ingres.COM>, by rog@Ingres.COM (Roger Taranto):
- > In article <1992Dec23.205149.2489@nntpd2.cxo.dec.com> alan@nabeth.enet.dec.com (Alan Rollow - Alan's Home for Wayward Tumbleweeds.) writes:
- >>[...] I've regularly run 128 MB systems with 25%
- >>buffer caches and those have worked fine. You do have to watch how
- >>you use delay_wbuffers with a large cache.
- >
- > So, what am I supposed to be watching the delay_wbuffers for?
-
- Long delays can result form having to write large buffer caches.
- Setting delay_wbuffers causes buffer writes to be delayed until update cause
- a flush of the buffer cache, so if the last period was mostly writes and
- a near full buffer cache and that cache is large then expect the system to pause
- every time update runs after a lot of disk writes have happened.
-
- Can be anoying.
-
- Cheers
- Mark :)
- --
- Mark Garrett Internet: mark@arvak.une.edu.au Phone: +61 66 20 3859
- University of New England, Northern Rivers, Lismore NSW Australia.
-