From: KADOTA Kyohei <lufia@me.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] fossil+venti performance question
Date: Tue, 5 May 2015 23:47:31 +0900 [thread overview]
Message-ID: <919294DB-2559-46FB-9800-DB0FBDB63AF6@me.com> (raw)
In-Reply-To: <A1D8C0A6-BB79-42EB-9874-C3F4A8FCC1F6@9srv.net>
Thanks Anthony.
> I bet if you re-run the same test twice in a
> row, you’re going to see dramatically improved
> performance.
I try to re-run ‘iostats md5sum /386/9pcf’.
Read result is very fast.
first read result is 152KB/s.
second read result is 232MB/s.
> Your write performance in that test isn’t really
> relevant: they’re not hitting the file system at all.
I think to write 1GB data to filesystem:
iostats dd -if /dev/zero -of output -ibs 1024k -obs 1024k -count 1024
Write result of dd is 31MB/s.
But this test may just write to fossil. It may not write to venti.
> I’m not sure why you’d see a difference in a
> fossil+venti setup of a different size, but the
> partition size relationships, and the in-memory
> cache size relationships, are what’s mostly important.
My hardware has 2GB memory.
Plan 9 configurations are almost default. (except /dev/sdC0/bloom)
To increase memory size is difficult,
because memory size is determined by public QEMU/KVM service plan.
—
kadota
next prev parent reply other threads:[~2015-05-05 14:47 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 9:32 KADOTA Kyohei
2015-05-04 16:10 ` Anthony Sorace
2015-05-04 18:11 ` Aram Hăvărneanu
2015-05-04 18:51 ` David du Colombier
2015-05-05 14:29 ` Sergey Zhilkin
2015-05-05 15:05 ` Charles Forsyth
2015-05-05 15:38 ` David du Colombier
2015-05-05 22:23 ` Charles Forsyth
2015-05-05 22:29 ` cinap_lenrek
2015-05-05 22:33 ` David du Colombier
2015-05-05 22:53 ` Aram Hăvărneanu
2015-05-06 20:55 ` David du Colombier
2015-05-06 21:17 ` Charles Forsyth
2015-05-06 21:26 ` David du Colombier
2015-05-06 21:28 ` David du Colombier
2015-05-06 22:28 ` Charles Forsyth
2015-05-07 3:35 ` erik quanstrom
2015-05-07 6:15 ` David du Colombier
2015-05-07 13:17 ` erik quanstrom
2015-05-08 16:13 ` David du Colombier
2015-05-08 16:39 ` Charles Forsyth
2015-05-08 17:16 ` David du Colombier
2015-05-08 19:24 ` David du Colombier
2015-05-08 20:03 ` Steve Simon
2015-05-08 21:19 ` Bakul Shah
2015-05-09 14:43 ` erik quanstrom
2015-05-09 17:25 ` Lyndon Nerenberg
2015-05-09 17:30 ` Devon H. O'Dell
2015-05-09 17:35 ` Lyndon Nerenberg
2015-05-09 21:54 ` Devon H. O'Dell
2015-05-09 18:20 ` Bakul Shah
2015-05-09 3:11 ` cinap_lenrek
2015-05-09 5:59 ` lucio
2015-05-09 16:26 ` cinap_lenrek
2015-05-09 16:23 ` erik quanstrom
2015-05-10 4:55 ` erik quanstrom
2015-05-10 5:07 ` erik quanstrom
2015-05-10 17:57 ` David du Colombier
2015-05-10 20:18 ` erik quanstrom
2015-05-10 20:19 ` cinap_lenrek
2015-05-10 20:51 ` erik quanstrom
2015-05-10 21:34 ` cinap_lenrek
2015-05-11 1:23 ` erik quanstrom
2015-05-09 16:59 ` erik quanstrom
2015-05-06 22:35 ` Steven Stallion
2015-05-06 23:47 ` Charles Forsyth
2015-05-07 3:38 ` erik quanstrom
2015-05-07 3:43 ` erik quanstrom
2015-05-05 15:07 ` KADOTA Kyohei
2015-05-05 14:47 ` KADOTA Kyohei [this message]
2015-05-05 15:46 ` steve
2015-05-05 15:54 ` David du Colombier
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=919294DB-2559-46FB-9800-DB0FBDB63AF6@me.com \
--to=lufia@me.com \
--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).