Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!tut.cis.ohio-state.edu!rutgers!cmcl2!edler
From: edler@cmcl2.NYU.EDU (Jan Edler)
Newsgroups: comp.unix.wizards
Subject: Re: Write-behind statistics wanted.
Keywords: write-behind, deleted files.
Message-ID: <35963@cmcl2.NYU.EDU>
Date: 12 Jan 89 20:16:27 GMT
References: <7819@boring.cwi.nl>
Reply-To: edler@cmcl2.UUCP (Jan Edler)
Organization: New York University, Ultracomputer project
Lines: 35

In article <7819@boring.cwi.nl> jack@cwi.nl (Jack Jansen) writes:
>Does anyone happen to have statistics around of the number of
>blocks that are written to disk that belong to files that have
>been removed already?

This topic came up once before, but I don't have a copy of my response
at that time.  This should be similar.

We optimize these away on our Ultracomputer prototypes.  We use the V7
filesystem with ordered writes and a 2KB blocksize.  We've configured
128 buffers into the system, and on a recent 3-day period, collected
the following data:

	number of buffer cache lookups:		1996814
	number of hits:				1722425 (86% hit rate)
	number of actual fs disk reads:		222451
	number of actual fs disk writes:	123421

	number of disk blocks freed:		56164
	number of those still in cache:		23188 (41%)
	number of those marked delayed write:	6639  (12% overall)

I don't know how typical our workload is, and this is just one data
point, but there it is.  12% of our disk blocks freed might have been
needlessly written to disk without our optimization, adding 1% to our
overall filesystem disk I/O rate.  Of course, some of them might have
been re-allocated and re-referenced again before being written to disk
anyway, but we do a sync every 45 seconds.

You decide how worthwhile it all is.

Jan Edler
NYU Ultracomputer Project
edler@nyu.edu
(212) 998-3353