Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site celerity.UUCP
Path: utzoo!linus!decvax!ittatc!dcdwest!sdcsvax!celerity!boston
From: boston@celerity.UUCP (Boston Office)
Newsgroups: net.arch
Subject: Re: IOCALL results and problems
Message-ID: <395@celerity.UUCP>
Date: Tue, 7-Jan-86 10:32:47 EST
Article-I.D.: celerity.395
Posted: Tue Jan  7 10:32:47 1986
Date-Received: Thu, 9-Jan-86 05:44:50 EST
References: <380@ncr-sd.UUCP> <835@bu-cs.UUCP>
Reply-To: boston@celerity.UUCP (Boston Office)
Organization: Celerity Computing, San Diego, Ca.
Lines: 18
Keywords: IOCALL, Multiuser

In article <835@bu-cs.UUCP> bzs@bu-cs.UUCP (Barry Shein) writes:
>Re: measuring multi-user system performance
>
>The only sane thing I have heard in years is what DEC is doing with
>ULTRIX (they say the method originated at AT&T) called Remote Terminal
>Emulation (RTE.)
>
>The basic idea is you put null modems on the tty mux's between two
>systems (the one being measured and another, spare.) You then run
>scripts through the mux from the spare machine and it records various
>performance benchmarks (eg. response time, service time etc.)
>
>Scripts can have random time distribution intervals so it needn't appear
>that everyone (say, 32 terminal lines) are banging at once, one can go
>so far as to simulate breaks etc by random long delays between type-ins.
>Measurement could be done for hours or even days.
>
Prime does this as well, using a tool called the Terminal Simulator.