Sponsored Content
Full Discussion: Athlon XP 1600+
UNIX Standards and Benchmarks UNIX & LINUX Benchmarks (Version 3.11) Linux Benchmarks Athlon XP 1600+ Post 52147 by GuizZzmo on Friday 11th of June 2004 04:47:20 AM
Old 06-11-2004
Athlon XP 1600+

System Notes:

CPU/Speed: AMD Athlon 1600+ 1.4Ghz
Ram: 768 MO DDR 333 PC2100
Motherboard: KG-7
Bus: PCI
Cache: 512KB
HD Controller: ?

Benchmarks:

==============================================================

BYTE UNIX Benchmarks (Version 3.11)
System -- Linux adsl.guizzzmo.com 2.6.3-7mdk #1 Wed Mar 17 15:56:42 CET 2004 i686 unknown unknown GNU/Linux
Start Benchmark Run: jeu jun 10 21:35:27 CEST 2004
0 interactive users.
Dhrystone 2 without register variables 1795488.5 lps (10 secs, 6 samples)
Dhrystone 2 using register variables 1757564.8 lps (10 secs, 6 samples)
Arithmetic Test (type = arithoh) 2861180.6 lps (10 secs, 6 samples)
Arithmetic Test (type = register) 164995.1 lps (10 secs, 6 samples)
Arithmetic Test (type = short) 161398.5 lps (10 secs, 6 samples)
Arithmetic Test (type = int) 116243.9 lps (10 secs, 6 samples)
Arithmetic Test (type = long) 99347.1 lps (10 secs, 6 samples)
Arithmetic Test (type = float) 314690.3 lps (10 secs, 6 samples)
Arithmetic Test (type = double) 357532.3 lps (10 secs, 6 samples)
System Call Overhead Test 815463.0 lps (10 secs, 6 samples)
Pipe Throughput Test 444876.2 lps (10 secs, 6 samples)
Pipe-based Context Switching Test 124085.4 lps (10 secs, 6 samples)
Process Creation Test 5287.4 lps (10 secs, 6 samples)
Execl Throughput Test 1345.1 lps (9 secs, 6 samples)
File Read (10 seconds) 1926886.0 KBps (10 secs, 6 samples)
File Write (10 seconds) 128252.0 KBps (10 secs, 6 samples)
File Copy (10 seconds) 47510.0 KBps (10 secs, 6 samples)
File Read (30 seconds) 2141400.0 KBps (30 secs, 6 samples)
File Write (30 seconds) 121130.0 KBps (30 secs, 6 samples)
File Copy (30 seconds) 34846.0 KBps (30 secs, 6 samples)
C Compiler Test 396.0 lpm (60 secs, 3 samples)
Shell scripts (1 concurrent) 743.6 lpm (60 secs, 3 samples)
Shell scripts (2 concurrent) 414.3 lpm (60 secs, 3 samples)
Shell scripts (4 concurrent) 213.0 lpm (60 secs, 3 samples)
Shell scripts (8 concurrent) 105.6 lpm (60 secs, 3 samples)
Dc: sqrt(2) to 99 decimal places 254816.8 lpm (60 secs, 6 samples)
Recursion Test--Tower of Hanoi 28208.4 lps (10 secs, 6 samples)


INDEX VALUES
TEST BASELINE RESULT INDEX

Arithmetic Test (type = double) 2541.7 357532.3 140.7
Dhrystone 2 without register variables 22366.3 1795488.5 80.3
Execl Throughput Test 16.5 1345.1 81.5
File Copy (30 seconds) 179.0 34846.0 194.7
Pipe-based Context Switching Test 1318.5 124085.4 94.1
Shell scripts (8 concurrent) 4.0 105.6 26.4
=========
SUM of 6 items 617.6
AVERAGE 102.9
 

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Athlon XP + Linux/Unix? and RAM Question

Has anyone had any experience with this new processor and its compatability with Linux/Unix? How did it preform comared to regular Athlons and P4's? I also have one other question. I plan on buying a new dell and fiddling left and right with it. Which type of RAM is better, RDRAM or... (3 Replies)
Discussion started by: KyPeN
3 Replies

2. UNIX for Dummies Questions & Answers

installing unix on a amd athlon processor

I just need a simple answer on if installing unix on a pc using an AMD processor instead of Intel is going to be a problem. Thank you one and all. (3 Replies)
Discussion started by: frznmeatcicle
3 Replies

3. Linux Benchmarks

Athlon XP3200 (@2236Mhz)

CPU/Speed: Athlon XP3200 @ 2236mhz Ram: 1GB DDR (344mhz) Motherboard: Abit NF7-S Cache: 512k on board Controller: Integrated Nforce2 Disk: 120Gb WD Special Edition, 40gb WD Caviar Load: 1 user. Clean boot, init 5 but X-Windows not loaded. Kernel: 2.6.5 pgms: gcc 3.2.3 Distribution:... (0 Replies)
Discussion started by: Garp
0 Replies
BPLAY(1)						      General Commands Manual							  BPLAY(1)

NAME
bplay, brec - buffered sound recording/playing SYNOPSIS
bplay [-d device] [-B buffersize] [-S] [-s speed] [-b bits] [[-t secs] | [-T samples]] [[-j secs] | [-J samples]] [-D level] [file] brec [-d device] [-B buffersize] [-S] [-s speed] [-b bits] [[-t secs] | [-T samples]] [-r|-v|-w] [-D level] [file] DESCRIPTION
bplay copies data from the named sound file (or the standard input if no filename is given) to the audio device. brec copies data from the audio device to the named sound file (or the standard output if no filename is present). These programs are intended to be drop-in replacements for the vplay and vrec programs by Michael Beck (beck@informatik.hu-berlin.de). OPTIONS -B buffersize Use the supplied audio buffer size instead of the default. -d device Use the supplied audio device instead of the default. -S Sound file is stereo. -s speed The speed in samples per second. -b bits The number of bits per sample. Only 8 and 16 are currently supported. -t secs The number of seconds to be played or recorded. -T samples The number of samples to be played or recorded. -j secs When playing, the number of seconds to skip at the beginning of the input before playing. -J samples When playing, the number of samples to skip at the beginning of the input before playing. -r When recording, write raw sound file. -v When recording, write Creative Labs VOC sound file. -w When recording write Microsoft Wave sound file. Note that the WAVE file format is limited to 4GiB filesize. Recording more data is possible, but the length info won't be consistent. -q Quiet mode. No messages are displayed. -D level Print debug information to stderr. Debug level ranges from 0 to 2, where 0 is no debug information. FILES
/dev/dsp The audio device. BUGS
The -t, -T, -j and -J options may do strange things when playing VOC files. There are limitations on recording VOC format files - specifically VOC files are only recorded in the 1.20 version of the format, which some player programs may choke on. There is also currently a limit of around 16M on the size of a VOC file which will be recorded. This is probably not a problem since I don't think anybody really uses VOC files anymore. This program prefers to run setuid root. This is because it wants to use setpriority() to run at the highest possible priority, and also locks down the buffers it uses to avoid them being swapped out. AUTHOR
David Monro (davidm@amberdata.demon.co.uk or davidm@cs.usyd.edu.au) The option parsing code was originally taken from vplay to maintain compatibility. 20 September 1999 BPLAY(1)
All times are GMT -4. The time now is 09:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy