From: matt@proweb.co.uk
To: 9fans@cse.psu.edu
Subject: RE: [9fans] General Question re Plan9 and wise hardware use
Date: Mon, 12 Jan 2004 15:12:14 +0000 [thread overview]
Message-ID: <81d2f74446228639a464c558e01ee9a1@juice.thebigchoice.com> (raw)
In-Reply-To: <004001c3d90b$97b8bc80$a8079486@RonRoberts>
While I agree that for multi-users where one will be cpu-ing to the server and running tasks there that slow terminals makes sense but my experience here as a single user made me make those assertions.
I ran an 800Mhz duron as the server and a 75Mhz Pentium as my diskless terminal.
The server mainly processes mail and serves as a gateway via 9fs to the remote servers via ftpfs & 9fs whereas my terminal runs rio, acme, anti-aliased fonts, multiple vnc windows, faces etc.
the p75 was a bit painful as my terminal. I did try it with cpu-ing to the Duron and running rio there but then the plumbing messed up and some other things messed up with regard to where files were expected to be and I didn't get a great overall improvement.
Swapping them over has solved all of the problems. My server does crawl a bit when I run my spam-deleting script (it only has 64Mb of ram!) but my terminal fair flies along, even in 1280x1024x16.
m
prev parent reply other threads:[~2004-01-12 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 12:36 Greg Pavelcak
2004-01-12 12:43 ` matt
2004-01-12 12:57 ` boyd, rounin
2004-01-12 15:12 ` matt [this message]
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=81d2f74446228639a464c558e01ee9a1@juice.thebigchoice.com \
--to=matt@proweb.co.uk \
--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).