How many BogoMips should I expect from my 486DX2 running Linux?

380 vues
Accéder directement au premier message non lu

Constantine Triantafillou

non lue,
17 oct. 1994, 02:11:0317/10/1994
à
Hi,


I have a 486DX2 66, and I was getting 33.7 BogoMips using Linux. Is
that reasonable?

Thanks
Constantine


--
*******************************************************************
*Constantine Triantafillou e-mail: tri...@pegasus.montclair.edu*
*"HELLAS=Science,Arts,Civilization,Democracy" *
*******************************************************************

Bill Sirinek

non lue,
17 oct. 1994, 15:45:1217/10/1994
à
In article <triant.7...@pegasus.montclair.edu>,
Constantine Triantafillou <tri...@pegasus.montclair.edu> wrote:

>I have a 486DX2 66, and I was getting 33.7 BogoMips using Linux. Is
>that reasonable?

Its in the FAQ...

Yes, 33.7 is correct, thats about what I get with my DX2/66

Don Bennett

non lue,
17 oct. 1994, 23:09:5817/10/1994
à
In article <37uk88$s...@news.cs.tulane.edu>,

Read the BogoMips-HOWTO. And I have ths same settup with 33.22 :)
--
"The human race is a remarkable creature, one with great potential, and I
hope that Star Trek has helped to show us what we can be if we believe
in ourself and our abilities." -Gene Roddenberry (1921-1991)
Don Bennett (dben...@cs.mun.ca, d...@engr.mun.ca) TIP#318

Beeblebrox

non lue,
19 oct. 1994, 15:11:1919/10/1994
à
tri...@pegasus.montclair.edu (Constantine Triantafillou) writes:

>I have a 486DX2 66, and I was getting 33.7 BogoMips using Linux. Is
>that reasonable?

Yes.

Derek Snider

non lue,
19 oct. 1994, 18:24:3419/10/1994
à
Constantine Triantafillou (tri...@pegasus.montclair.edu) wrote:
: Hi,


: I have a 486DX2 66, and I was getting 33.7 BogoMips using Linux. Is
: that reasonable?

Seems to me that bogomips don't mean diddly...
I get more bogomips on a 486DX2 66 than on a P60 (33.x vs. 26.x)

---------------------------------------------------------------------
Telnet to our mud ... Realms of Despair ---> mud.compulink.com 4000
Or join our International Teleconference ---> chat.compulink.com 9000

Thomas Blidung

non lue,
24 oct. 1994, 17:26:2924/10/1994
à
sir...@cs.tulane.edu (Bill Sirinek) writes:

>Its in the FAQ...


There was long ago a list of BOGOMIPS

here is it once again.
tom

From: ba...@clifton.hobby.nl
Subject: BogoMips Mini-HOWTO
Keywords: BogoMips, kernel
Newsgroups: comp.os.linux.announce
Approved: linux-a...@tc.cornell.edu (Matt Welsh)

BOGOMIPS(tm) MINI-HOWTO
Wim C.A. van Dorst <ba...@clifton.hobby.nl>
13 April 1994


>From Lars Wirzenius' mail of 9 September 1993, explaining Bogomips:

MIPS is short for Millions of Instructions Per Second. It is a
measure for the computation speed of a program. Like most such
measures, it is more often abused than used properly (it is very
difficult to justly compare MIPS for different kinds of computers).

BogoMips are Linus's invention. The kernel (or was it a device
driver?) needs a timing loop (the time is too short and/or needs to be
too exact for a non-busy-loop method of waiting), which must be
calibrated to the processor speed of the machine. Hence, the kernel
measures at boot time how fast a certain kind of busy loop runs on a
computer. "Bogo" comes from "bogus", i.e, something which is a fake.
(See the Jargon File for more information.) Hence, the BogoMips value
gives some indication of the processor speed, but it is way too
unscientific to be called anything but BogoMips.

The reasons (there are two) it is printed during bootup is that a) it
is slightly useful for debugging and for checking that the computers
caches and turbo button work, and b) Linus loves to chuckle when he
sees confused people on the news.


>From Ian Jackson's List of Frequently asked questions,
amended by himself at 23 January 1994, and from private mail from
Przemek Klosowski at 29 March 1994

As a very approximate guide the BogoMips will be approximately:

386SX clock * 0.125 + 0.2
386DX clock * 0.20 - 0.6
486Cyrix/IBM clock * 0.22 + 4.
486SX/DX clock * 0.49 + 0.25
486DX2 clock * 0.50 + 0.37
Pentium 24.0

If the number you're seeing is wildly lower than this you may have the
Turbo button or CPU speed set incorrectly, or have some kind of
caching problem


Let me add that there are only two reasons for paying attention
to the Bogomips rate that is presented on booting Linux:

1. To see whether it is in the proper range for the particular
processor, its clock frequency, and the potentially present cache.
Especially 486 systems are prone to faulty setups of RAM caching,
turbo-buttons, and such things.

2. To see whether your system is faster than mine. Of course
this is completely wrong, unreliable, ill-founded, and utterly
useless, but all benchmarks suffer from this same problem. So
why not use it? This inherent stupidity has never before stopped
people from using benchmarks, has it? :-)


The following are some reported Bogomips rates for various systems.

A. Oddly or faulty configured 386 systems

System Bogomips Reporter
386DX/16 387 nocache 0.57 H. Peter Anvin <h...@ahab.eecs.nwu.edu>
386/16 Zenith 0.67 H. Peter Anvin <h...@ahab.eecs.nwu.edu>
386DX/25 0.82 Philip Wright <philip...@purplet.demon.co.uk>
386DX/25 nocache 1.03 Mark A. Horton <mah...@crl.com>
386SX/16 1.5 Stefan Kromer <s...@galaxy.sunflower.sub.org>
386SX/16 2.23 Steven M. Gallo <smg...@cs.buffalo.edu>
386SX/16 turbo 2.38 Andrew Haylett <a...@gec-mrc.co.uk>
386DX/25(?) 128c 6.03 Chuck Meo <m...@solbourne.com>

B. Normal 386 SX systems

System Bogomips Reporter
386SX/16 Packard Bell 2.05 <root@Belvedere\%hip-hop.suvl.ca.us>
386SX/16 2.15 Warren Stevens <wgst...@undergrad.math.uwaterloo.co>
386SX/16 2.2 Lech Marcinkowski <puo...@tekla.fi>
386SX/16 2.23 Andrew Bulhak <a...@yoyo.cc.monash.edu.au>
386SX/16 nocache 2.43 Adam Clarke <ad...@loose.apana.org.au>
386SX/20 2.7 Alex Strasheim <astr...@nyx.cs.du.edu>
386SXL/25 AMD 2.9 Vaughan R. Pratt <pr...@Sunburn.Stanford.EDU>
386SX/25 AMD nocache 3.06 K.J. MacDonald <ke...@festival.ed.ac.uk>
386SX/25 AMD 3.38 Hamish Coleman <ham...@zot.apana.org.au>
386SL/25 Intel 3.57 Stephen Harris <har...@teaching.physics.ox.ac.uk>
386SX/25 AMD 3.62 Stephen Harris <har...@teaching.physics.ox.ac.uk>
386SX/33 Intel 4.06 Kenneth J. Hoover <k...@PSUEDVAX.PSU.EDU>
386SX/33 4.71 Alexander Pet. Komlik <ap...@l.ukrcom.kherson.ua>

C. Normal 386 DX systems

System Bogomips Reporter
386DX/20 Intel 3.0 Malcolm Reeves <ree...@rocky1.usask.cs>
386DX/20 Intel 3.08 Stephen Harris <har...@teaching.physics.ox.ac.uk>
386DX/20 Nec Powermate 3.22 David J Dawkins <dav...@isl.co.uki>
386DX/20 3.67 Joost Helberg <jhel...@nlsun8.oracle.nl>
386DX/25 3.91 Ian McCloghrie <imcc...@cs.ucsd.edu>
386DX/25 3.95 Grant Edwards <gra...@aquarius.rosemount.com>
386DX/25 32cache 4.53 Jussi M.A. Lahtinen <jmal...@klaava.Helsinki.FI>
386DX/33 5.86 Tim Lacy <ti...@microsoft.com>
386DX/33 64cache 5.99 Lars Wirzenius <wirz...@kruuna.Helsinki.FI>
386DX/33 Intel 5.99 Harri Pasanen <hpas...@cs.hut.fi>
386DX/33 no387 6.03 Joel B.Levin <le...@bbn.com>
386DX/33 387 6.03 Peter Bechtold <pe...@fns.greenie.muc.de>
386DX/33 387 256cache 6.65 Wim van Dorst <ba...@clifton.hobby.nl>
386DX/40 6.99 Ken Wilcox <wil...@math.psu.edu>
386DX/40 AMD 7.10 Kerry Person <kpe...@plains.NoDak.edu>
386DX/40 7.10 Dhaliwal Bikram Singh <a336...@cdf.toronto.edu>
386DX/40 128cache 7.23 Julian Francis Day <jf...@aber.ac.uk>
386DX/40 bogoboosted 7.23 Pat St Jean <stj...@math.enmu.edu>
386DX/40 AMD 128cache 7.23 Ralf Bergs <ra...@akela.informatik.rwth-aachen.de>
386DX/40 7.29 Eric Chris Garrison <er...@nickel.ucs.indiana.edu>
386DX/40 7.29 Darin Cowan <co...@rubicon.org>
386DX/40 7.29 Bonne van Dijk <bo...@cs.utwente.nl>
386DX/40 AMD 387 64c 7.91 <wi...@gnu.ai.mit.edu>
386DX/40 AMD 32c 7.98 Tommy Olsen <tom...@ifi.uio.no>
386DX/40 7.98 Christian Nelson <cne...@csugrad.cs.vt.edu>

D. Oddly or faulty configured 486 systems

System Bogomips Reporter
486DX/33 nocache 1.45 Mark Gray <vata...@gvu1.gatech.edu>
486DLC/40 nocache 2.45 Steven Schendel <ssc...@magnus.acs.ohio-state.edu>
486DX/33 3.61 Marten van de Laan <mar...@cs.rug.nl>
486DX/33 noturbo 3.61 Dimitris Evmorfopoulos <devm...@mtu.edu>
486DX/33 256c noturbo 4.25 Wouter Liefting <wlie...@cs.vu.nl>
486DX/33 4.66 Mark Gray <vata...@gvu1.gatech.edu>
486Rx2 Cyrix 25/50 4.85 <cosc...@menudo.uh.edu>
486SX/33 noturbo 5.21 Scott D. Heavner <s...@fishmonger.nouucp>
486SLC Cyrix 7 Pieter Verhaeghe <pi...@uia.ac.be>
486DLC/33 387DX/40 9.47 Denis Solaro <dr...@vectrex.login.qc.ca>

E. Cyrix/IBM configured 486 systems

System Bogomips Reporter
486DLC/33 Cyrix 386 11.2 Alex Freed <fr...@europa.orion.adobe.com>
486DLC/40 256c 11.33 Steven Schendel <ssc...@magnus.acs.ohio-state.edu>
486DRx2/40 Cyrix 13.10 Christopher Lau <cl...@acs.ucalgary.ca>
486DLC/40 bogoboost 13.21 Harry Pasanen <p...@tekla.fi>
486DLC/40 487 Cyrix 13.21 Ian A. Verschuren <i...@po.CWRU.Edu>
486DCL Cyrix 13.3 Tracer Bullet P.I. <g...@earth.baylor.edu>
486DLC/40 13.31 Adam Frampton <fram...@access2.digex.net>
486DLC/40 13.31 Rick Chow <c...@cacs.usl.edu>
486SLC2/25 14.6 Vaughan R. Pratt <pr...@Sunburn.Stanford.EDU>
486DLC/40 TI 128c 15.97 Philip K. Roban <ph...@seal.micro.umn.edu>
486DRx2 20/40 15.99 Christopher Lau <la...@fusion.cuc.ab.ca>
486SLC2/66 IBM 64c 18.95 Sujat Jamil <su...@shasta.ee.umn.edu>
486SLC2/66 IBM 128c 18.95 Sujat Jamil <su...@shasta.ee.umn.edu>
486SLC2/66 19.02 Harry Mangalam <mang...@uci.edu>

F. Normal 486 systems

System Bogomips Reporter
486SX/20 DECpc 9.98 Thomas Pfau <pf...@cnj.digex.com>
486SX/25 12.24 Michael Buchenrieder <mi...@scrum.greenie.muc.de>
486SX/25 12.42 Mark R. Lindsey <mlin...@nyx.cs.du.edu>
486DX/25 12.5 Phillip Hardy <phi...@mserve.kiwi.gen.nz>
486DX/33 15.8 H. Peter Anvin <h...@ahab.eecs.nwu.edu>
486DX/33 64cache 16.1 H. Peter Anvin <h...@ahab.eecs.nwu.edu>
486DX/33 256c 16.33 Eric Kemminan <ekem...@pms709.ms.ford.com>
486DX/33 16.35 Christopher L. Morrow <cm...@andrew.cmu.edu>
486DX/33 256c DIY 16.44 Wouter Liefting <wlie...@cs.vu.nl>
486DX/33 Intel 128c 16.44 Rafal Kustra <g1kr...@cdf.toronto.edu>
486DX/33 16.5 Alex Freed <fr...@europa.orion.adobe.com>
486DX/33 16.6 Vaughan R. Pratt <pr...@Sunburn.Stanford.EDU>
486DX/33 noturbo 16.61 Chris Vetter <cbve...@rbg.informatik.th-darmstadt.de>
486DX/33 16.61 Jeffrey L. Newbern <jnew...@athena.mit.edu>
486DX/33 16.61 M. Heuler <heu...@cip.informatik.uni-wuerzburg.edu>
486DX/33 16.61 Frank Lofaro <ftlo...@unlv.edu>
486DX/40 19.8 Jose Calhariz <c...@minerva.inesc.pt>
486DX/40 19.91 M. Heuler <heu...@cip.informatik.uni-wuerzburg.edu>
486DX/40 Intel 19.97 Paul van Spronsen <vs...@teppic.sun.ac.za>
486DX/40 19.97 Ulf Tietz <u...@rio70.bln.sni.de>
486DX/40 19.97 <Eberhard\_Moenk...@p27.rollo.central.de>
486DX/33 turbo 19.98 Chris Vetter <cbve...@rbg.informatik.th-darmstadt.de>
486DX/50 24.48 Arnd Gehrmann <arnd@rea>
486DX/50 AMD 24.85 Klaas Hemstra <h...@mh.nl>
486DX/50 DTK 24.85 Randolph Christophers <ran...@lna.oz.au>
486DX/50 24.85 Kevin Lentin <kev...@bruce.cs.monash.edu.au>
486DX2/50 24.85 Jason Matthew <jmat...@kn.pacbell.com>
486DX/50 25 Robert Herzog <rhe...@rc1.vub.ac.be>
486DX2/50 25.0 Christian Holtje <cho...@ux1.cso.uiuc.edu>
486DX2/50 DECpc 25.04 Thomas Pfau <pf...@cnj.digex.com>
486DX/50 25.10 M. Heuler <heu...@cip.informatik.uni-wuerzburg.edu>
486DX2/66 33 Alec Muffett <al...@uk-usenet.uk.sun.com>
486DX2/66 33 Steve Tinney <s...@enlil.museum.upenn.edu>
486DX2/66 33.2 H. Peter Anvin <h...@ahab.eecs.nwu.edu>
486DX2/66 33.20 Arnd Gehrmann <arnd@rea>
486DX2/66 33.22 Brian Ricker <gt2...@prism.gatech.edu>
486DX2/66 33.3 Devon Tuck <de...@netcom.com>
486DX2/66 256cache 33.4 H. Peter Anvin <h...@ahab.eecs.nwu.edu>
486DX2/66 33.5 Jongyoon Lee <m...@netcom.com>
486DX2/66 33.55 <al...@minster.york.ac.uk>
486DX2/66 ICL 33.55 Mathias Koerber <mat...@solomon.technet.sg>
486DX2/66 256c Intel 33.81 Stephen Harris <har...@teaching.physics.ox.ac.uk>
486DX2/66 34.06 Al Clark <acl...@netcom.com>
486DX2/80 39.94 Danny ter Haar <da...@caution.cistron.nl.mugnet.org>
486DX2/80 40.0 Rick Brown <cca...@prism.gatech.edu>

G. Other systems

System Bogomips Reporter
68030/25 Amiga 3000 6.21 Hamish Macdonald <ham...@bnr.ca>
68040/24 Amiga 4000/40 16.6 Hamish Macdonald <ham...@bnr.ca>
Pentium 23.96 Joost Helberg <jhel...@nlsun8.oracle.nl>
Pentium 23.96 Ulf Tietz <u...@rio70.bln.sni.de>
Pentium/60 Gateway 23.96 Manoj Kasichainula <mvka...@eos.ncsu.edu>
Pentium/60 NCR 3455 24 Mathias Koerber <mat...@solomon.technet.sg>

This overview was compiled by me, while my wife is gone to
pregnancy gymnastics tonight. I guess monitoring c.o.l.* for
BogoMips ratings will decline in the near future.

Met vriendelijke groeten, Wim van Dorst.
---------------------------------------------------------------------
Blue Baron = Wim van Dorst, Voice (+31) 074-443937, (+31) 02152-42319
(-: ba...@clifton.hobby.nl tgc...@urc.tue.nl W...@Akzo.400net.nl :-)
---------------------------------------------------------------------

--
-----------------------------------------------------------------------------
| Thomas Blidung, Dueneberger Strasse 58a, D-21502 Geesthacht |
| EMail: <ro...@umibox.hanse.de> Voice: +49-4152-82393 |
| umibox.hanse.de : +49- 4152-82493 Fax : +49-4152-82493 |

William Henning

non lue,
21 oct. 1994, 02:45:3321/10/1994
à
In article <3846b2$2...@news.compulink.com> de...@cid.compulink.com (Derek Snider) writes:

>Constantine Triantafillou (tri...@pegasus.montclair.edu) wrote:
>: I have a 486DX2 66, and I was getting 33.7 BogoMips using Linux. Is
>: that reasonable?
>
>Seems to me that bogomips don't mean diddly...
>I get more bogomips on a 486DX2 66 than on a P60 (33.x vs. 26.x)

Yep, and I get 39.94 on my new Amd486DX2-80

Bill


--
----

bhen...@bhami.wimsey.com - Linux & OS/2 user at home, OS/2 developer at work

Répondre à tous
Répondre à l'auteur
Transférer
0 nouveau message