From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil+venti continuous disk activity
Date: Thu, 23 Mar 2006 12:38:17 -0500 [thread overview]
Message-ID: <794f77b6ad37c299fe74831e40e5225b@swtch.com> (raw)
In-Reply-To: <db8eee8a5c7c1d948c84de650d285b50@terzarima.net>
sorry, i should have said more.
locking up for 10 minutes straight is not common behavior,
but in the scenario you described, it's to be expected.
fossil was in the middle of archiving its first snapshot
to disk. let's call that 250MB. the distributed venti is
robust but quite slow -- four long disk seeks per
write if you are running index and arenas on the same disk.
on a single disk i expect around 1-3GB/hour. so 10 minutes
for that 250MB is entirely within the ballpark.
as forsyth noted, during archive snapshots fossil usually
does respond to requests, but you explicitly told it not to
by running fshalt. it didn't finish halting until the archive
was done. i suppose halt could stop the archiver and
let it pick up again later. but it doesn't.
russ
next prev parent reply other threads:[~2006-03-23 17:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 17:08 Skip Tavakkolian
2006-03-23 17:10 ` Russ Cox
2006-03-23 17:18 ` veritosproject
2006-03-23 17:20 ` Russ Cox
2006-03-23 17:22 ` veritosproject
2006-03-23 17:29 ` Ronald G Minnich
2006-03-23 17:29 ` Gabriel Diaz
2006-03-23 17:30 ` andrey mirtchovski
2006-03-23 17:31 ` Charles Forsyth
2006-03-23 17:36 ` andrey mirtchovski
2006-03-23 17:43 ` Gabriel Diaz
2006-03-23 18:12 ` veritosproject
2006-03-23 18:51 ` Charles Forsyth
2006-03-23 17:37 ` Skip Tavakkolian
2006-03-23 17:41 ` Gabriel Diaz
2006-03-23 17:38 ` Russ Cox [this message]
2006-03-23 17:16 ` David Leimbach
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=794f77b6ad37c299fe74831e40e5225b@swtch.com \
--to=rsc@swtch.com \
--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).