9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Speed of 9pfuse on Linux
Date: Wed, 10 Feb 2010 10:28:30 -0600	[thread overview]
Message-ID: <A49BC633-AAA7-439F-8ECB-099E24FED3FB@gmail.com> (raw)
In-Reply-To: <83c63c25-5d91-4bc1-910d-4e8402ccda40@g28g2000yqh.googlegroups.com>


On Feb 10, 2010, at 7:32 AM, Pavel Klinkovsky wrote:

>> 1) real plan9 to the same place
>> 2) qemu plan9 on Fedora to the same place
> As I wrote above, I made exactly the same test on exactly the same HW
> (and internet connection).
> 1. Native Plan9.
> 2. Native Fedora 10 with p9p.
> 
>> "It's slow, what's wrong" is perhaps a little vague.
> Not precisely measured (I can do it today).
> My estimation of the time spent by 'ls' command in contrib directory:
> - 9pfuse on Fedora was more than 10 times slower.
> 

That's actually probably pretty good, if you look at slide  10 & 11 on my Linux 9P Trace and Walkthrough (top of http://www.graverobber.org at the moment) you'll see the bad protocol behavior caused by v9fs at the moment -- 9pfuse probably has around the same order increase.  The problem is that Linux doesn't know we got all the attribute information with the dirread, and then goes and individually queries each file in the directory with a stat -- this happens in a serial fashion, so the high latency to sources just makes the problem worse.

A potential solution is to cache metadata, which would speed things up dramatically for static data, but might mess things up for synthetic files.

      -eric




  reply	other threads:[~2010-02-10 16:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10  9:27 Pavel Klinkovsky
2010-02-10  9:54 ` Gorka Guardiola
2010-02-10 12:28   ` Eric Van Hensbergen
2010-02-10 13:32   ` Pavel Klinkovsky
2010-02-10 11:57 ` Pavel Klinkovsky
2010-02-10 13:04   ` Eric Van Hensbergen
2010-02-10 12:09 ` maht
2010-02-10 13:32 ` Pavel Klinkovsky
2010-02-10 16:28   ` Eric Van Hensbergen [this message]
2010-02-10 16:44     ` Steve Simon
2010-02-10 18:54       ` Venkatesh Srinivas
2010-02-10 19:46         ` Gorka Guardiola
2010-02-12 10:53         ` Pavel Klinkovsky
2010-02-12  8:20           ` Jacob Todd
2010-02-12 11:25           ` roger peppe
2010-02-12 12:15           ` Pavel Klinkovsky
2010-02-12 12:45             ` Eric Van Hensbergen
2010-02-12 17:51               ` Tim Newsham
2010-02-12 18:07                 ` Abhishek Kulkarni

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=A49BC633-AAA7-439F-8ECB-099E24FED3FB@gmail.com \
    --to=ericvh@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).