9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: <tt.gustavsson@bredband.net>
To: <9fans@cse.psu.edu>
Subject: [9fans] Process distribution?
Date: Sun, 23 May 2004 11:33:23 +0200	[thread overview]
Message-ID: <20040523093323.CKQX14728.mxfep02.bredband.com@mxfep02> (raw)


if you have say 5 cpu servers in your network, how do you choose wich server to run
applications in? Would you logically dedicate them to different types of tasks, like
compilation server,  graphics processing, ... , or dedicate them to different groups
of people, the programmers in the building across the street, and the programmers in
the same building... ?

It is an elegant distributed computing environment, and I am curious of how to
use it effectively. The idea seems too not be intended in this environment,
and my idea was to deal with two different issues:

1. many terminals connecting to a couple of cpu servers, were you would not actively
choose which cpu to use for certain programs.

2. Somehow use a number of cpu servers for raw cpu processing (seti and such...)

(I just realized that the second issue really does not apply to my idea).

Anyway, I will set up an old dual Ppro as my first CPU server, interestingley enough.


Cheers

/Tony G









             reply	other threads:[~2004-05-23  9:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-23  9:33 tt.gustavsson [this message]
2004-05-23 13:17 ` a
  -- strict thread matches above, loose matches on Subject: below --
2004-05-27  4:48 YAMANASHI Takeshi
2004-05-21 11:37 tt.gustavsson
2004-05-21 13:24 ` a
2004-05-21 14:22   ` Fco.J.Ballesteros
2004-05-21 15:18     ` boyd, rounin
2004-05-21 15:25       ` Fco. J. Ballesteros
2004-05-21 15:29         ` boyd, rounin
2004-05-22  0:54     ` ron minnich
2004-05-21 14:27 ` boyd, rounin
2004-05-21 22:04 ` Geoff Collyer

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=20040523093323.CKQX14728.mxfep02.bredband.com@mxfep02 \
    --to=tt.gustavsson@bredband.net \
    --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).