From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] More venti sync woes.
Date: Thu, 27 Sep 2007 19:03:59 -0400 [thread overview]
Message-ID: <01387c9397134fc04134154232a11821@quanstro.net> (raw)
In-Reply-To: <509071940709271549l57a778e5k9d0f70e3d3a670be@mail.gmail.com>
> as for my venti config: i'll confirm when i get thin thing booted off
> another medium, but from memory: i've got a ~30GB fossil partition, a
> 64MB bloom filter, a 5-10GB index, and a ~120GB arenas partition.
> there's also a 9fat and swap in there somewhere. it's all on one disk.
> i certainly appreciate the fact that non-dma disks can be dog slow
> under load. but at this point, whatever it's doing it's been doing for
> over 24 hours; even a factor of 50 puts that at just under half an
> hour to reboot, which seems like an unreasonable amount of time for a
> server to spin on an unclean reboot. what was the rough improvement
> factor you observed?
generally, a sata disk is good for 30-50 MB/s using sequential
IDE dma transfers on the outer tracks. /non-sequential access
can be as slow as non-dma access./
(i fixed a similar problem reciently with the on-disk cache of ken's fs.
throughput went up by a factor of 20 or so.)
russ would have to answer questions about disk access patterns with
venti, but you could be generating constant seeks between the various
partitions.
- erik
next prev parent reply other threads:[~2007-09-27 23:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 19:32 Anthony Sorace
2007-09-26 19:39 ` Steve Simon
2007-09-26 19:41 ` erik quanstrom
2007-09-26 19:49 ` Anthony Sorace
2007-09-27 21:53 ` Russ Cox
2007-09-27 22:49 ` Anthony Sorace
2007-09-27 23:03 ` erik quanstrom [this message]
2007-09-28 3:16 ` Russ Cox
2007-09-28 9:01 ` Kernel Panic
2007-09-28 16:35 ` Anthony Sorace
2007-09-27 23:54 ` Charles Forsyth
2007-09-28 0:10 ` erik quanstrom
2007-09-28 0:19 ` Charles Forsyth
2007-09-28 0:19 ` erik quanstrom
2007-09-28 4:01 ` Bruce Ellis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01387c9397134fc04134154232a11821@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).