9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kfs performance
Date: Wed,  3 Mar 2004 14:15:08 -0500	[thread overview]
Message-ID: <E1Aybpo-000Fug-UQ@t40.swtch.com> (raw)
In-Reply-To: Your message of "Wed, 03 Mar 2004 09:48:56." <418ebcba5700419ea957ef3bf7392b19@juice.thebigchoice.com>

> "For metadata intensive benchmarks this improves performance by more than a f
> actor of two when compared to the conventional syncronous write approach"
> 
> hget http://www.ece.cmu.edu/~ganger/papers/CSE-TR-254-95/CSE-TR-254-95.ps

except that extracting a 200MB file is anything but metadata intensive.



  parent reply	other threads:[~2004-03-03 19:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-02 14:15 David Tolpin
2004-03-02 14:27 ` matt
2004-03-02 14:55 ` ron minnich
2004-03-02 15:34 ` gdiaz
2004-03-03  2:19 ` Russ Cox
2004-03-03  2:31   ` Jeff Sickel
2004-03-03  8:52   ` Charles Forsyth
2004-03-03  9:23     ` David Tolpin
2004-03-03 10:35     ` matt
2004-03-03  9:48   ` matt
2004-03-03  9:51     ` David Tolpin
2004-03-03 19:15     ` Russ Cox [this message]
2004-03-03 19:28       ` C H Forsyth

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=E1Aybpo-000Fug-UQ@t40.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).