Date: Fri, 29 Oct 1999 08:02:28 -0700 (PDT) From: "Jonathan M. Bresler" <jmb@hub.freebsd.org> To: peter.jeremy@alcatel.com.au Cc: freebsd-arch@freebsd.org Subject: Re: Storing small files in inodes Message-ID: <19991029150228.BB45314BF7@hub.freebsd.org> In-Reply-To: <99Oct29.085056est.40332@border.alcanet.com.au> (message from Peter Jeremy on Fri, 29 Oct 1999 08:55:57 %2B1000)
next in thread | previous in thread | raw e-mail | index | archive | help
> > >I vaguely remember a paper on the topic. > I was sure I wasn't the first one to think of this. > http://www.usenix.org/publications/library/proceedings/ana97/ganger.html With embedded inodes, the inodes for most files are stored in the directory with the corresponding name, removing a physical level of indirection without sacrificing the logical level of indirection. With explicit grouping, the data blocks of multiple small files named by a given directory are allocated adjacently and moved to and from the disk as a unit in most cases. Measurement for our C-FSS implementation show that embedded inodes and explicit grouping have the potential to increase small file throughput (for both reads and writes) by a factor of 5-7 compared to the same file system without these techniques. The improvement comes directly from reducing the number of disk accesses required by an order of magnitude. Preliminary experience with software-development applications shows performance improvements ranging from 30-300 percent. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991029150228.BB45314BF7>