From: Jack Johnson <fragment@nas.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] small boxed PC and dual CPU file server?
Date: Fri, 19 Jul 2002 08:54:30 -0700 [thread overview]
Message-ID: <3D383636.3020802@nas.com> (raw)
In-Reply-To: <134a1c844a8343c74b1e3bb833af00c6@plan9.bell-labs.com>
jmk@plan9.bell-labs.com wrote:
> The current filesystem code makes makes no use of extra CPUs on Intel
> platforms. However, the new filesystem stuff we are working on will.
Could you go into a little more detail about that?
In my limited experience, file service tends not to be bound by CPU
(unless you're running Microsoft software), but by disk I/O and network
throughput.
Unless you're trying to saturate Gigabit Ethernet, I suppose. But even
then, by my estimation a 1.6GHz P4 should be able to handle that
(assuming the various busses can keep up, and I'd shudder to think what
you spent on disk to sustain that).
Multiprocessor support could be very nice for older hardware, though.
-Jack
next prev parent reply other threads:[~2002-07-19 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 15:16 jmk
2002-07-19 15:54 ` Jack Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-19 18:35 jmk
2002-07-19 18:18 David Gordon Hogan
2002-07-19 18:13 jmk
2002-07-19 16:36 jmk
2002-07-19 16:54 ` Doc Shipley
2002-07-19 20:28 ` cnielsen
2002-07-19 16:01 bwc
2002-07-19 16:08 ` Doc Shipley
2001-07-18 23:04 okamoto
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=3D383636.3020802@nas.com \
--to=fragment@nas.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).