From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Thu, 5 Jan 2012 16:31:00 -0500 To: 9fans@9fans.net Message-ID: In-Reply-To: References: <20120105124852.GA940@polynum.com> <20120105144810.182add7c@wks-ddc.exosec.local> <20120105151518.GB435@polynum.com> <74f17bd79e5a709683d94e72b4459623@lvoc.net> <20120105184858.87B0BB858@mail.bitblocks.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] venti and "contrib": RFC Topicbox-Message-UUID: 561d9e9a-ead7-11e9-9d60-3106f5b1d025 On Thu Jan 5 16:24:58 EST 2012, yarikos@gmail.com wrote: > 2012/1/5 Bakul Shah : > > You'd save a bunch of energy if you only powered up venti > > disks once @ 4AM for a few minutes (and on demand when you > > look at /n/dump). =C2=A0Though venti might have fits! And the disks > > might too! So may be this calls for a two level venti? First > > to an SSD RAID and a much less frequent venti/copy to hard > > disks. >=20 > I think you're confusing kenfs+worm with fossil+venti in sense that > ken fs is a complete cache for worm while fossil is a write cache for > venti. You need venti running all the time. this only could work if you assume that everything in the worm is also in the cache, and you've configured your cache to cache the worm. since these days the cache is often similar in performance to the worm, t= he default we use is to not copy the worm into the cache. this would just result in more i/o. so tl;dr you need the worm available at all times be it venti+fossil or ken fs/cwfs - erik