9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: john@csplan9.rit.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Experiences with remote connections?
Date: Sat, 16 Jun 2007 05:27:20 -1000	[thread overview]
Message-ID: <d1cdb20b0244268d57ec627b80a6b95f@csplan9.rit.edu> (raw)
In-Reply-To: <20070616193156.327001E8C22@holo.morphisms.net>

>> ramfs seems to improve lc by about a second
>> or two. Still far from what I'd consider acceptable,
>> which is unfortunate; once a program is loaded,
>> it runs very nicely and responsively. Maybe it
>> would be more feasible simply to boot the terminal
>> from its own disk, then import my mailbox and
>> mount my fileserver to /n/csplan9 so I can access
>> my files.
>
> mc is accessing all sorts of odd files that i'd
> forgotten about (it reads files in /lib/font to
> figure out string widths to insert tabs correctly
> to make the columns line up).  try just comparing
> ls with and without the ramfs -- that should be
> more representative of what cfs can do.
>
> i've booted over a few hundred miles before
> and also over an early cable modem (28.8k up
> via phone line, 1M down via cable) and it was
> okay once cfs got going.  the real test is to make
> a cache partition and try cfs directly.
>
> russ

I set up a 200 MB partition for cfs; it seems to be helping
a bit. rio on the cpu server works okay too. I'll just have
to see which I end up using more.
Thanks!


John



  reply	other threads:[~2007-06-16 15:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16 12:41 john
2007-06-16 18:59 ` Russ Cox
2007-06-16 13:11   ` john
2007-06-16 19:31     ` Russ Cox
2007-06-16 15:27       ` john [this message]
2007-06-16 19:42       ` andrey mirtchovski
2007-06-16 20:28         ` geoff
2007-06-16 22:12   ` Francisco J Ballesteros
2007-06-16 20:18 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=d1cdb20b0244268d57ec627b80a6b95f@csplan9.rit.edu \
    --to=john@csplan9.rit.edu \
    --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).