From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <d24bbddcadcf6d7067215e0f27c1e541@collyer.net>
From: Geoff Collyer <geoff@collyer.net>
Date: Fri, 21 May 2004 15:04:30 -0700
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Process distribution?
In-Reply-To: <20040521113733.LDBQ14728.mxfep02.bredband.com@mxfep02>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 8439b124-eacd-11e9-9e20-41e7f4b1d025

I think you want a little more control over where programs run.
The canonical examples are that editors are better suited to
terminals and compilers to CPU servers.  CPU servers are not
necessarily all equivalent, even within an installation.

The cpu command takes a second or two to start the named
command running (depending upon the complexity of your profile)
so it's often simpler to just run `cpu' to create a window
running an rc on a CPU server, or run `cpu -c rio' to run a
window system there.

I have rarely felt slowed by a CPU server being overloaded,
so I'm not sure that there's a real problem here.