Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/5/84; site omen.UUCP Path: utzoo!linus!decvax!tektronix!reed!omen!caf From: caf@omen.UUCP (Chuck Forsberg WA7KGX) Newsgroups: net.micro,net.micro.pc,net.unix Subject: Latest "bc" benchmark results Message-ID: <298@omen.UUCP> Date: Wed, 12-Feb-86 16:58:21 EST Article-I.D.: omen.298 Posted: Wed Feb 12 16:58:21 1986 Date-Received: Fri, 14-Feb-86 07:26:03 EST Distribution: net Organization: Omen Technology, Portland Lines: 64 Xref: linus net.micro:12596 net.micro.pc:6739 net.unix:6547 *** REPLACE THIS LINE WITH YOUR BENCHMARK *** A Quickie Benchmark for Unix Systems Revised Feb-12-86 Chuck Forsberg Omen Technology INC The following benchmark was recommended by some folks from National Semiconductor as they felt the siev benchmark with its tight loops "discriminated" againgst highly pipelined CPU's. It's also very easy to type in, and catches some of the botches in alleged "clones" of Unix(TM). On unbundled systems, bc and an editor are almost always included in the "bacic package", so lack of a C compiler need not preclude running this benchmark. If the system cannot run this benchmark, it probabaly lacks something else YOU need to get your work done. Unless otherwise noted, the file "bct" was created with vi, chmod executable, and run as the shall script shown. Although not stated here, you can get a good idead of a system's responsiveness by going through these steps. Bct gives a reasonable indication of how quickly a machine processes compute intensive tasks such as troff and compiler passes. DISCLAIMER: Vendors are constntly improving their products by making them both faster and more compatible with the Real Unix. If you see a machine with bad results, consider it a warning and not condemnation. time bc <