From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Why are some apps so slow?
Date: Sat, 23 Sep 2006 09:32:17 -0400 [thread overview]
Message-ID: <ee9e417a0609230632q6913251cx57dba00b17adc3f1@mail.gmail.com> (raw)
In-Reply-To: <8ccc8ba40609221321w3dd7dc55m6747aa3c67d057cd@mail.gmail.com>
> Anyone actually studied this? Anyone considered replacing this with, say,
> put/get rpcs that do it all? In some cases there are multiple read (or write),
> rounds, but many times, I see the 4 rpcs just to get a bunch of bytes.
> This was a concern for us while using omero across slow network links.
Of course, one easy solution to this is to keep the file descriptor
open for more than one read or write. Then it's just one round trip.
Russ
next prev parent reply other threads:[~2006-09-23 13:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 5:31 John Floren
2006-09-22 5:54 ` Skip Tavakkolian
2006-09-22 6:08 ` Anselm R. Garbe
2006-09-22 11:43 ` erik quanstrom
2006-09-22 13:49 ` jmk
2006-09-22 15:02 ` C H Forsyth
2006-09-22 20:21 ` Francisco J Ballesteros
2006-09-23 13:32 ` Russ Cox [this message]
2006-09-23 13:47 ` Francisco J Ballesteros
2006-09-23 14:55 ` Russ Cox
2006-09-23 15:00 ` Francisco J Ballesteros
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=ee9e417a0609230632q6913251cx57dba00b17adc3f1@mail.gmail.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).