Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:1149 comp.os.linux:55776
Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!ogicse!netnews.nwnet.net!news.clark.edu!spool.mu.edu!bloom-beacon.mit.edu!senator-bedfellow.mit.edu!jfc
From: jfc@athena.mit.edu (John F Carr)
Newsgroups: comp.os.386bsd.misc,comp.os.linux
Subject: Re: FYI.. benchmarks on linux and 386bsd
Keywords: benchmarks speed downers uppers and other dirty laundry
Message-ID: <28rm1i$os2@senator-bedfellow.MIT.EDU>
Date: 5 Oct 93 11:33:06 GMT
Article-I.D.: senator-.28rm1i$os2
References: <2CB12A8D.17397@news.service.uci.edu> <2CB12C2F.23255@news.service.uci.edu>
Organization: Massachusetts Institute of Technology
Lines: 7
NNTP-Posting-Host: porter.mit.edu
30% is a large enough difference that it might be caused by incorrect
definition of the clock tick rate (depending on how the program measures
time). A pure CPU benchmark shouldn't change that much (unless the
cache is disabled when running Linux?).
--
John Carr (jfc@athena.mit.edu)