The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: johnh@psych.usyd.edu.au (John Holden)
Subject: [pups] thrust meter?
Date: Tue, 10 Oct 2006 09:02:08 +1000	[thread overview]
Message-ID: <1AC552DD-C287-4001-A5BC-95DD1092ACA8@psych.usyd.edu.au> (raw)
In-Reply-To: <Pine.BSI.4.61.0610052143300.19364@dave.horsfall.org>


On 05/10/2006, at 10:15 PM, Dave Horsfall wrote:

> On Wed, 4 Oct 2006, Brian Knittel wrote:
>
>> The thrust meter project -- was that an analog meter that displayed %
>> CPU utilization? I remember that Tom Ferrin had one mounted in the
>> middle of a DEC panel filler on the 11/70 at the Computer Graphics  
>> Lab
>> at UCSF. It was really delightful having this analog meter  
>> bouncing up
>> and down as people worked away.
>
> It integrated the BUS BUSY signal over a suitable time constant  
> (and my
> electronics knowledge is a bit too rusty to figure out Tc, but with a
> 10uF tantalum capacitor I imagine it would be a few seconds).

Um, depends what you mean by thrust. It was originally designed for a  
11/45
where bus activity would have been a fare indication of machine load  
since
all memory and i/o used the unibus (I'm excluding the effects of fastbus
memory on 11/50 and 55's).

The 11/70 unibus was actually slower than the 11/45, and generally  
didn't
have memory or disk/tape i/o on it (separate memory bus and massbus). So
'thrust' was probably mainly character i/o (dh and dz's) and older
disk/tapes (RK05's etc)

Now, where's 11/70 maintenance printset?

Cheers
John




  reply	other threads:[~2006-10-09 23:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05  4:17 Brian Knittel
2006-10-05 12:15 ` Dave Horsfall
2006-10-09 23:02   ` John Holden [this message]
2006-10-10  9:05     ` Johnny Billquist
2006-10-10 11:00       ` Dave Horsfall
2006-10-10 22:20         ` John Holden
2006-10-10 10:55     ` Dave Horsfall

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=1AC552DD-C287-4001-A5BC-95DD1092ACA8@psych.usyd.edu.au \
    --to=johnh@psych.usyd.edu.au \
    /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).