From: Matt Pidd-Cheshire <axwrt001@yahoo.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] It's not like lightning is it ...
Date: Tue, 8 Jun 2004 18:09:39 -0700 [thread overview]
Message-ID: <40C66353.1040805@yahoo.com> (raw)
Brantley Cole wrote:
> Does the program in question buffer its output?
> Plan 9 doesn't like lots of small writes.
The tree is built during the input read phase and
written when the input is exhausted through a stdio
interface. 9 days and counting for the read phase, it
didn't even get round to writing.
The bottleneck seems to be kfs' reading the fresh data.
Fat kfs buffers don't solve the initial read problem,
the system generally is a bit slicker once the data is
cached.
next reply other threads:[~2004-06-09 1:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 1:09 Matt Pidd-Cheshire [this message]
2004-06-09 1:13 ` Rob Pike
-- strict thread matches above, loose matches on Subject: below --
2004-06-08 22:12 Matt Pidd-Cheshire
2004-06-08 22:17 ` boyd, rounin
2004-06-08 23:07 ` Matt Pidd-Cheshire
2004-06-08 23:32 ` Brantley Coile
2004-06-08 21:37 Matt Pidd-Cheshire
2004-06-07 22:08 ` Charles Forsyth
2004-06-08 22:43 ` Matt Pidd-Cheshire
2004-06-08 22:54 ` Geoff Collyer
2004-06-08 21:42 ` boyd, rounin
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=40C66353.1040805@yahoo.com \
--to=axwrt001@yahoo.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).