From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: [9fans] Fossil/venti performance (Was: Sources Gone?)
Date: Tue, 3 Feb 2009 20:37:16 +0200 [thread overview]
Message-ID: <753b3c2c5060c2ef38f39dbcd6c788d0@proxima.alt.za> (raw)
In-Reply-To: <bc558135619964bf7556b911dd21600e@quanstro.net>
> i would imagine that cpu has nothing to do with it and encryption
> would add no overhead at all. i would image that seeks dominate
> your performance numbers.
Well, there are numerous issues. The machine is a CPU server booting
off another fossil/venti host; it has its own rather pristine, mostly
unused Plan 9 distribution and a few other fossil partitions of which
only one is backed by venti. I am hesitantly initialising the dump
partition because I'm not convinced I have the efficient direcory
hierarchy I want to live with.
I can't easily check before fossil is active, but venti takes a long
time to start and by the time the machine is "ready", memory is full
and half of swap is in use :-( During "snap -a" load, context
switching and interrupts tend to swing wildly and swap is often being
accessed (it's on IDE and the drive light can only mean swap access, I
do have DMA active :-)
So I would not use this particular configuration to win any
competitions.
In passing, the first time I did this, I powered the machine down a
few times because I was convinced it had stalled. That might have
been pessimism on my part, because now that I am monitoring it
(stats), it is clear that it occasionally shows no sign of disk
activity (no seek, load in astronomical places) for long periods, only
to proceed again later.
But I do turn all snaptimes to none, which I superstitiously did the
first time and seemed to make a difference (I bet it didn't, but if
anyone suspects that a dump should finish before another starts, I
have the equipment to test the theory.
++L
next parent reply other threads:[~2009-02-03 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bc558135619964bf7556b911dd21600e@quanstro.net>
2009-02-03 18:37 ` lucio [this message]
2009-02-03 18:44 ` erik quanstrom
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=753b3c2c5060c2ef38f39dbcd6c788d0@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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).