
	Where results make sense

Topic: Whetstone (benchmark)

Related Topics

Benchmark

Dhrystone

Khornerstone

KDF9

LINPACK

TOP500

CPU architecture

Computer architecture

Aquamark

Hint

TPC

Fhourstones

Cochrane District, Ontario

National Physical Laboratory

System of linear equations

In the News (Mon 16 Nov 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	CPU-World: Explanation of benchmarks
		For this benchmark sound and mouse are disabled, screen details are set to "High", screen size is set to full screen with a status bar (one level before max screen size).
		For this benchmark sound and mouse are disabled, screen details are set to "Low", screen size is set to full screen with a status bar (one level before max screen size).
		This benchmark is running immediately after Doom (high detail) benchmark, the results are taken three times, the average of these results is the final number.
	www.cpu-world.com /info/bench/benchmarks.html (405 words)

	Whetstone (benchmark) - Wikipedia, the free encyclopedia
		The Whetstone benchmark is a benchmark for evaluating the performance of computers.
		The Whetstone benchmark primarily measures the floating-point arithmetic performance.
		A similar benchmark for integer and string operations is the Dhrystone.
	en.wikipedia.org /wiki/Whetstone_(benchmark) (182 words)

	A Language-Independent Set of Benchmarks for Parallel Processors
		The Whetstone benchmark [2], for example, is speciÞcally designed to defeat attempts to vectorize, parallelize, or pipeline the code.
		Even the Whetstone benchmark was originally intended as a weighted mean of several operations, with different sets of weights for different application mixes; yet the only numbers ever used are the default weights suggested by Curnow and Wichmann [2].
		Benchmarks are often criticized as being too short to represent very large application programs, and this is particulary valid if one is measuring a machine with a program cache.
	www.scl.ameslab.gov /Publications/Gus/6-pack/6-pack.html (4340 words)

	Linux Benchmarking - Concepts
		The original Whetstone benchmark was designed in the 60's by Brian Wichmann at the National Physical Laboratory, in England, as a test for an ALGOL 60 compiler for a hypothetical machine.
		The version of the Whetstone benchmark that we are going to use for this example was slightly modified by Al Aburto and can be downloaded from his excellent FTP site dedicated to benchmarks.
		Whetstone is not a Linux specific test, it's not even an OS specific test, but it certainly is a good test for the FPU in your Linux box, and also gives an indication of compiler efficiency for specific kinds of applications that involve FP calculations.
	linuxgazette.net /issue22/bench.html (2555 words)

	Q-Bench Help (Site not responding. Last check: 2007-10-11)
		Q-bench's implementation of the Whetstone benchmark allows each module to be run individually, or combined as a single benchmark.
		As is the case in all current implementations of Whetstone benchmarks, modules 1, 5, and 10 are omitted.
		This set of benchmarks is used to test the memory bandwidth and efficiency of memory management on a Microsoft Windows® CE device.
	www.autopcware.com /qbench.htm (1542 words)

	comp.benchmarks FAQ
		Benchmarks are commonly used to predict the performance of an unknown system on a known, or at least well-defined, task or workload.
		Benchmarks are frequently used to ensure the minimum level of performance in a procurement specification.
		Benchmarks are often used to measure general things like graphics, I/O, compute (integer and floating point), etc., performance, but most measure more specific tasks like rendering polygons, reading and writing files, or performing operations on matrixes.
	www.cs.wisc.edu /~thomas/comp.benchmarks.FAQ.html (5368 words)

	HICSS98
		Benchmarks are used by the marketing divisions of computer manufacturers in the belief that they predict value of the computer (real or perceived) to the customer and can be used as a factor in pricing strategies.
		This is the scalable benchmark that we conjecture may be a superset of other popular benchmarks, since it presents the full range of memory hierarchy performance whereas other benchmarks pick a particular problem size and measure execution time [6, 7].
		These are assorted integer and floating-point benchmarks [1] that serve mainly as examples of too-small problems for the purpose of this study.
	www.scl.ameslab.gov /Publications/Gus/HICSS98/HICSS98.html (5401 words)

	CmpSci 635 Lecture 3
		Benchmarks have been created to serve as standard codes that can be tried on different machines for comparison purposes.
		The Whetstone benchmark is a collection of codes originally written in Algol 60 that test floating point math library performance.
		Unfortunately, Whetstone has been recoded in other languages over the years, in both single and double precision, and "improved" from time to time (sometimes in ways that favored particular machines) so that it is almost impossible to compare one Whetstone rating to another.
	www.cs.umass.edu /~weems/CmpSci635/635lecture3.html (3505 words)

	PERFORMANCE of VARIOUS COMPUTERS in COMPUTATIONAL CHEMISTRY
		Benchmark results from both machine are included in this report, together with those from the 16-way Regatta HPC node (in which one of the dual core CPUs is disabled), and the 1 GHz power4 CPU in the 4-way IBM eServer pSeries 630/6C4.
		In the MATRIX-89 benchmark, the matrices were of order 10, 20, 30,..., 100, the summed CPU times of Table 10 referring to 100 diagonalizations of order 10 matrices, 90 of order 20 matrices, and so on up to 10 diagonalizations for matrices of order 100.
		The benchmark is specifically designed to work with datasets much larger than the available cache on any given system, so that the results are (presumably) more indicative of the performance of very large, vector style applications.
	www.cfs.dl.ac.uk /benchmarks/compchem.html (8712 words)

	[No title]
		The Dhrystone benchmark exists in equivalent Ada, Pascal and C versions, which are all available from netlib@ornl.gov. Dhrystone measures the time to execute its main loop and sets this time into relation with a fixed reference time, the result being a performance index given in "Dhrystones per second".
		The four parts of the WINTACH benchmark were then modeled after these profiles, so that the percentage of certain GDI (graphics device interface) calls found in the profiles is also present in the benchmark.
		Whetstone performance depends on the speed of the coprocessor as well as on the speed of the CPU, while LLL and Linpack place a heavier burden on the coprocessor/FPU.
	www.textfiles.com /computers/cpucmp14.txt (4238 words)

	What is Whetstone? CPU Benchmark Integer Performance Mflops (Site not responding. Last check: 2007-10-11)
		A comparison of the single processor Whetstone performance on a variety of machines, including vector supercomputers, minisupers, super-workstations and workstations, together with that obtained on a number of vector CPUs and on single nodes of various MPP machines.
		The primary aim of this benchmark is to provide a performance measure of both floating point (FP) and integer arithmetic; thus while trends in the VL Mflop ratings are of interest, only a small part of the total CPU time is actually involved in these operations.
		Results from the older MATRIX-89 benchmark are no longer listed as the overall run times are so small on the current generation of hardware to be of little use.
	bugclub.org /beginners/processors/whetstone.html (210 words)

	Whetstone Benchmark History and Results
		Brian Wichmann modified the interpreter to record statistics on the intermediate Whetstone instructions and produced a suite of simple statements which could be used to evaluate the efficiency of compilers and overall performance of a processor (see ICL KDF9 benchmark results in the table - the first is for the Whetstone Interpreter).
		By this time, the Whetstone benchmark speed rating had become the default definition of minicomputer MIPS (Millions of Instructions Per Second), its significance being exaggerated when a minicomputer supplier somehow acquired the table of Whetstone benchmark results and published some of them in the computer press with the heading "Now who has the fastest minicomputer".
		Whetstone performance ratings are known to have been a serious consideration in the design of the Digital VAX systems and other minicomputers of the same vintage, where some were reluctant to publish double precision results which did not match VAX speeds.
	homepage.virgin.net /roy.longbottom/whetstone.htm (2176 words)

	[No title]
		ó¨Benchmarks and Benchmarking¡(¨µIn the early 1980s, Xerox corporation, a leader in benchmarking, define it as the continuous process of measuring products, services, and practices against the toughest competitors.¡¶Nhó¨Benchmarks and Benchmarking¡(¨5Benchmarks, in contrast to benchmarking, are measurements to evaluate the performance of a function, operation or business relative to others.
		In the electronic industry, for instance, a benchmark has long referred to an operating statistics that allows you to compare your own performance to that of another.¡6Z6ó0-¨-RELATION OF BENCHMARKS WITH EMPIRICAL METHODS¡..(¨In many areas of Computer sciences, experiments are the primary means of demonstrating the potential and value of systems and techniques.
		The advantage is that the weakness of any one benchmark is lessened by the presence of the other benchmarks.
	www.cs.fit.edu /~jpmcgee/classes/CSE5800/BENCHMARKS.ppt (1177 words)

	The Whetstone Benchmarks
		Whetstone is a benchmark test which attempts to measure the speed and efficiency at which a computer performs floating-point operations.
		The Whetstone is a synthetic benchmark designed to measure the behavior of scientific programs.
		The primary aim of this benchmark is to measure the performance of both integer and floating-point arithmetic.
	www.keil.com /benchmarks/whetstone.asp (112 words)

	[Boinc_opt] comparison Compiled Vs Download
		Next, Benchmark code (and I suspect all recent Whetstone benchmarks) was cheating.
		Not intentionally on the benchmark designer or boinc developer's parts, but because the optimizing compiler was too clever for OUR own good.
		And the benchmark was supposed to give us an idea of how long such things would really take.
	www.ssl.berkeley.edu /pipermail/boinc_opt/2004-September/000033.html (236 words)

	Benchmark Test - Unofficial BOINC Wiki
		However, in the case of the BOINC Software this is less of an issue in that the point of the benchmark is to calculate a rough metric of contribution and not an exact quantity for qualitative comparisons.
		The Whetstone Benchmark does 8 different groups of tests (repeatedly of course), times how long they took to finish, and pops out a number.
		Almost all the time in the Whetstone Benchmark is used for trigonometry.
	boinc-wiki.ath.cx /index.php?title=Benchmark (725 words)

	United Devices Benchmarking Myths (Site not responding. Last check: 2007-10-11)
		One of the contributing factors to this benchmark is the speed of your processor.
		The benchmark that United Devices has chosen to use as its metric is the "Whetstone" benchmark, which focuses on a large variety of floating-point math operations, which is what many scientific research applications are at least partially dependant upon.
		The Whetstone benchmark is a convenient choice because it allows you to judge overall computational power using an industry-standard term known as a "flop", or floating-point operation.
	www.bovine.net /~jlawson/united-devices/benchmyth (2297 words)

	Dr. Dobb's \| A Benchmark Apologia \| July 22, 2001
		Benchmarkers must be sensitive to the need for compilers to be compared on equal terms.
		The Whetstone benchmark also exhibits a frustrating lack of verifiability, because it produces no output that you can check but performs many complex operations that open the door to a lot of potentially wrong answers.
		The Loop benchmark was originally created to factor out loop overhead in benchmarks that used loops to artificially increase a benchmark's running time rather than increase the number of operations at the source level.
	www.ddj.com /184408083;jsessionid=FTZUAL3KNZ1WIQSNDLQSKHSCJUNN2JVN?_requestid=1045913 (3881 words)

	[No title]
		This benchmark is written in Fortran with an interface to Unix written in C and emphasizes memory and program flow.
		VGX benchmark Whetstone This is a synthetic workload representing a mix of floating point, procedure call, transcendental functions, etc. that make up a typical scientific workload.
		The original Whetstone benchmark was written in Algol by Curnow and Wichman at the U.K.'s National Physical Laboratory in Whetstone, England.
	www.unf.edu /public/cda4102/ychua/bench/bench.descriptions.faq (2352 words)

	SiSoftware Zone
		While the original benchmark does not compute anything, this version does check the results with the expected ones just in case there are problems with the CPU/memory.
		A: The Whetstone benchmark is widely used in the computer industry as a measure of FPU or Co-Processor performance.
		The Whetstone benchmark used here is a multi-threaded, 32/64-bit variant of the original one which runs under UNIX.
	www.sisoftware.co.uk /index.html?dir=qa&location=ben_cpu&langx=en&a= (1870 words)

	[H] Enthusiast - (Site not responding. Last check: 2007-10-11)
		The Whetstone portion is used to measure the processor's FPU, or Math Co-Processor, and once again the result is determined by the amount of time it takes to complete sequences of the floating point instructions.
		The Whetstone benchmark used here is a multi-threaded, 32-bit variant of the original one which runs under UNIX.
		The SSE2 Whetstone benchmark is needed here to show you how the P4 deals with needed FPU instruction.
	www.hardocp.com /article.html?art=Nywy (1003 words)

	BenchMark - BOINC - Trac
		'Whetstone' is the name of the benchmark that is reported on your [Show computers] web page as 'Measured floating point speed'.
		Dhrystone is the name of the benchmark used for 'Measured integer speed'.
		Whetstone does 8 different groups of tests (repeatedly of course), times how long they took to finish, and produces a number, [ops performed]/[time].
	boinc.berkeley.edu /trac/wiki/BenchMark (455 words)

	NSCEE - TeraBit Newsletter Vol.7 No.3
		A benchmark is a test that measures the performance of a computer system or subsystem on a well-defined task or set of tasks.
		The eight benchmark problems are specified in a "pencil and paper" fashion, leaving benchmarkers free to select the language constructs and implementation techniques best suited for a particular system.
		This benchmark was created by the CSRD division at NSCA and is a collection of 13 scientific and engineering Fortran programs (full-sized, real-life programs) comprising over 60,000 lines of code (fluid dynamics, molecular dynamics, signal processing, circuit simulation, etc.) It is specifically targeted for evaluating supercomputer performance.
	www.nscee.edu /Publications/Newsletters/TeraBit_Oct97/survey.html (658 words)

	Whetstone - Wikipedia, the free encyclopedia
		Whetstone (brook) - A brook running through Craftsbury, Vermont, USA.
		Whetstone Creek is a tributary of the Olentangy River in NE Ohio in the United States.
		Whetstone Chocolates - A manufacturer of gourmet chocolates based in St.
	en.wikipedia.org /wiki/Whetstone (185 words)

	BenchMarks
		In the final analysis benchmarks based on end-user tasks are the only real test of a system and will form the basis of acceptance tests carried out during system installation (to ensure that the requirements specification is satisfied).
		In general the SPEC benchmarks are suitable for comparing the performance of high performance workstations and nodal processors for specialist scientific or engineering numeric processing.
		In particular it is important to remember that 'standard' benchmarks should only be used as an initial filter to identify those systems and configurations which appear to meet the computational requirements of the application, i.e.
	www.cse.dmu.ac.uk /~bb/Teaching/ComputerSystems/SystemBenchmarks/BenchMarks.html (3883 words)

	How To Compile Optimized BOINC Client for Linux
		These benchmark scores are then used in conjunction with the time taken to process a work unit to calculate how much credit your computer will claim for that work unit.
		The Whetstone benchmark tests double precision maths and spends the majority of it's time performing trigonometric functions whereas SETI performs almost all single precision maths and typically only spends about 20% of it's time performing trigonometric functions.
		Thirdly, none of these estimates or benchmarks take into account factors such as memory bandwidth or processor cache size which SETI is hugely dependant on and can make a significant difference to raw performance.
	www.pperry.f2s.com /boinc-credit.htm (674 words)

	[No title]
		Using a clever yet simple formula, the Ackermann benchmark is able to execute millions of non-redundant calls, while using a modest amount of stack space.
		The Whetstone benchmark program was originally written in Algol 60 to measure the performance of an early computer built at the Whetstone laboratory in the UK.
		The result is a number of Whetstone instructions per second, and is weighted to represent a typical contemporary scientific program.
	www.xgc.com /benchmarks/benchmarks.htm (358 words)

	Target PC :: Intel Pentium III Coppermine FC-PGA
		The benchmark is designed to contain a representative sample of types of operations, mostly numerical, used by applications.
		According to the Sisoft FAQ: The Sandra Whetstone benchmark is widely used in the computer industry as a measure of FPU or Co-Processor performance.
		The Whetstone benchmark used here is a 32-bit variant of the original one which runs under UNIX.
	www.targetpc.com /hardware/cpu/coppermine/index3.shtml (310 words)

Try your search on: Qwika (all wikis)