From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <161be1432da8336b773065a911095bc2@quanstro.net> References: <6a3ae47e0908140145r2ccbdf54xe3ed1eeca598d9ea@mail.gmail.com> <161be1432da8336b773065a911095bc2@quanstro.net> Date: Fri, 14 Aug 2009 13:44:45 +0100 Message-ID: <6a3ae47e0908140544m7792bf29i955e76bd9944d8da@mail.gmail.com> From: Robert Raschke To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=002354530668bbf3df0471196a63 Subject: Re: [9fans] file server? Topicbox-Message-UUID: 4954af2a-ead5-11e9-9d60-3106f5b1d025 --002354530668bbf3df0471196a63 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On Fri, Aug 14, 2009 at 1:07 PM, erik quanstrom wrote: > > The venti archive starts at 2AM, and my cron job is at 4AM. So far, I've > not > > yet had an archive take longer than 2 hours. But that's partly due to > > triggering one explicitly after a pull that's just replaced all my > > executables ;-) > > that's surprising to me that it would take that long. > is that typical? > > just on the back of the proverbial envelope ... > a completely seek-bound disk with 8k blocks > gets ~3mb/s even when diabolicly seek bound, > lets take something way more pessimistic > like 0.5mb/s for 1 hr = 1800mb. > > 180mb dumps would still be large, so you > must be getting on the order of 50kb/s > dumps? > > i'm not a venti expert, but i find it hard to believe > that venti would be that slow normally. do you > need to resize memory or your bloom filter? > > hope my display of ignorance here doesn't > seem like criticism. > > - erik > > I am running an old (pre bloom) venti on a 500MHz VIA with some crappy no-name 30GB PATA drive. But, yes, I would be surprised if an archival dump took longer than a few minutes (from looking at my logs anything from 45sec to 4.5min is typical, but I haven't looked at the amounts of data). Saying that, those pulls from a while ago, where pretty much the whole file tree got replaced did lead to a dump taking almost an hour. Robby --002354530668bbf3df0471196a63 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Fri, Aug 14, 2009 at 1:07 PM, erik quanst= rom <quanstro= @quanstro.net> wrote:
> The venti archive starts at 2AM, and my cron job is = at 4AM. So far, I've not
> yet had an archive take longer than 2 hours. But that's partly due= to
> triggering one explicitly after a pull that's just replaced all my=
> executables ;-)

that's surprising to me that it would take that long.
is that typical?

just on the back of the proverbial envelope ...
a completely seek-bound disk with 8k blocks
gets ~3mb/s even when diabolicly seek bound,
lets take something way more pessimistic
like 0.5mb/s for 1 hr =3D 1800mb.

180mb dumps would still be large, so you
must be getting on the order of 50kb/s
dumps?

i'm not a venti expert, but i find it hard to believe
that venti would be that slow normally. =C2=A0do you
need to resize memory or your bloom filter?

hope my display of ignorance here doesn't
seem like criticism.

- erik


I am running an old (pre bloom) venti on a 50= 0MHz VIA with some crappy no-name 30GB PATA drive. But, yes, I would be sur= prised if an archival dump took longer than a few minutes (from looking at = my logs anything from 45sec to 4.5min is typical, but I haven't looked = at the amounts of data).

Saying that, those pulls from a while ago, where pretty much the whole = file tree got replaced did lead to a dump taking almost an hour.

Rob= by

--002354530668bbf3df0471196a63--