From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] fs performance
Date: Mon, 10 Jan 2011 06:45:12 -0800 [thread overview]
Message-ID: <AANLkTi=+HXi6-U4423QO85o+wmO+pckX9C0+QkKWqxxp@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikSFvfi-r0qm-bF7PGq0sSayyRBGAD9Z3ySpdsq@mail.gmail.com>
On Sunday, January 9, 2011, ron minnich <rminnich@gmail.com> wrote:
> On Sun, Jan 9, 2011 at 1:38 PM, Bakul Shah <bakul+plan9@bitblocks.com> wrote:
>
>> I didn't say plan9 "suffers". Merely that one has to look at
>> other aspects as well (implying putting in Tstream may not
>> make a huge difference).
>
> well, what we do know from one set of measurements is that it makes a
> measurable difference when latency is measured in the tens of
> milliseconds. :-)
>
> I have done some of these other measurements, e.g. system call
> overhead. Plan 9 system call time is quite a bit longer than Linux
> nowadays, when Linux uses the SYSENTER support.
Linux maps the kernel in the high 1GB of VM too doesn't it? What does
Plan 9 do (haven't looked yet)
>
> At the same time, the Plan 9 "mon" device that Andrey wrote was
> considerably faster than the procfs-based "mon" device I wrote: 30K
> samples/second on Plan 9 vs. 12K samples/second on Linux.
>
> John did do some measurement of file system times via the trace device
> we wrote. I think it's fair to say that the IO path for fossil is
> considerably slower than the IO path for kernel-based file systems in
> Linux: slower as in multiples of 10, not multiples. There's a fair
> amount of copying, allocation, and bouncing in and out of the kernel,
> and this activity does not come cheap.
>
> So, one speculation is that a kernel-based Plan 9 file system might be
> quite fast. And that's enough random text for a Sunday.
Well number of syscalls to hand off delegating filesystem tasks to a
userspace filesystem implementation is key. Microkernels try to
optimize this as do virtualization hypervisors, because, as observed,
bouncing around between kernel and userspace gives performance hopes
the beat-down.
>
> ron
>
>
next prev parent reply other threads:[~2011-01-10 14:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 17:06 erik quanstrom
2011-01-09 17:29 ` ron minnich
2011-01-09 17:51 ` John Floren
2011-01-10 18:07 ` Francisco J Ballesteros
2011-01-10 18:48 ` hiro
2011-01-10 19:06 ` erik quanstrom
2011-01-10 19:53 ` John Floren
2011-01-11 11:33 ` hiro
2011-01-09 18:31 ` erik quanstrom
2011-01-09 19:54 ` Bakul Shah
2011-01-09 20:25 ` ron minnich
2011-01-09 20:47 ` erik quanstrom
2011-01-09 21:04 ` ron minnich
2011-01-09 21:17 ` Bakul Shah
2011-01-09 21:59 ` erik quanstrom
2011-01-09 22:58 ` Charles Forsyth
2011-01-09 22:55 ` ron minnich
2011-01-09 23:50 ` Charles Forsyth
2011-01-10 3:26 ` Bakul Shah
2011-01-09 21:14 ` erik quanstrom
2011-01-09 21:38 ` Bakul Shah
2011-01-09 21:56 ` ron minnich
2011-01-09 22:02 ` erik quanstrom
2011-01-10 14:45 ` David Leimbach [this message]
2011-01-10 15:06 ` Charles Forsyth
2011-01-09 22:00 ` erik quanstrom
2011-01-10 3:57 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='AANLkTi=+HXi6-U4423QO85o+wmO+pckX9C0+QkKWqxxp@mail.gmail.com' \
--to=leimy2k@gmail.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).