02-27-2006
Mistake in caculating Benchmark Average
There is a basic principal that you cannot average averages. The overall result for the benchmark should be calculated by dviding the sum of the target results by the sum of the baseline results. This is not the same as dividing the sum of the index results by 6. Changing the way this is calculated will give a more mathematically valid way of comparing performance from one host to the other.
8 More Discussions You Might Find Interesting
1. UNIX Benchmarks
CPU/Speed: Ultrasparc IIi / 300MHz
Ram: 128MB (Not enough)
Motherboard: Sun Ultra 5/10
Bus: 4 PCI
Cache: 512K Ecache
Controller: Onboard IDE ATA/33
Disk: 40GB IBM ATA/100
Load: Low, 1 user, apache, samba, ipf, dtlogin disabled.
Kernel: Solaris 5.10 b72
Kernel ELF?: yes
pgms: I used the... (0 Replies)
Discussion started by: 98_1LE
0 Replies
2. UNIX Benchmarks
AMD-K5 Processor at 133Mhz
32MB RAM
5 GB Hard Drive
10MB NIC
1MB ARC Graphics Card
PS/1 Keyboard
CD-ROM
Floppy Drive
Kickin' Fast BABY! hehe
BYTE UNIX Benchmarks (Version 3.11)
System -- FreeBSD evil-linux.net 5.0-RELEASE FreeBSD 5.0-RELEASE #0: Thu Jan 16 22:16:53 GMT 2003... (0 Replies)
Discussion started by: Phobos
0 Replies
3. Linux
I work in a computer company which sells computer configurations and parts of them. And I want to give a choice to customers. If they want to buy a PC with Linux installed, not Windows. But I find difficult to test the Graphic Cards in Linux OS. I have searched the web and I didn't found any... (2 Replies)
Discussion started by: vlatkop
2 Replies
4. UNIX Benchmarks
Hi,
Is there a precompiled binary for Solaris 8 available?
I need to bench mark our Oracle server,
as we are upgrading from SFv880 to SFv890.
Both are fully loaded.
I can't find a sun machine that I can compile the software on.
Tks
JohnHo (0 Replies)
Discussion started by: John Ho
0 Replies
5. UNIX Benchmarks
CPU: 1 x PA8600, 440MHz
RAM: 1GB
Hardware model: 9000/800/N4000-44
BYTE UNIX Benchmarks (Version 3.11)
System -- HP-UX xxx B.11.11 U 9000/800 615379343 unlimited-user license
Start Benchmark Run: Tue Apr 4 05:43:42 IST 2006
1 interactive users.
Dhrystone 2 without register... (0 Replies)
Discussion started by: blowtorch
0 Replies
6. AIX
Hi,
I needed space on a FS, and when I've added the space on the filesystem, I did it trough the regular smitty fs inteface and not with smitty cl_lvm.
Can someone help me to repair the situat before a faileover happen ?
Thanks for your help,:mad: (13 Replies)
Discussion started by: azzed27
13 Replies
7. UNIX Benchmarks
Type: UltraSPARC IIIi 1,593 Mhz x2
Ram: 16G
Disk: 2*70G fw scsi drives
Load: db application
kernel: Sunos5.10
pgms: compiled Sun cc -O2
==============================================================
BYTE UNIX Benchmarks (Version 3.11)
System -- SunOS sun.spmbox.com 5.10... (2 Replies)
Discussion started by: mr_manny
2 Replies
8. UNIX for Dummies Questions & Answers
Hi there can anyone help me to spot my mistake and please explain why it appears
My code :
#!/usr/bin/gawk -f
BEGIN { bytes =0}
{ temp=$(grep "datafeed\.php" | cut -d" " -f8)
bytes += temp}
END { printf "Number of bytes: %d\n", bytes }
when I am running ./q411 an411
an411:
... (6 Replies)
Discussion started by: FUTURE_EINSTEIN
6 Replies
sum(1) General Commands Manual sum(1)
NAME
sum - Displays the checksum and byte count in block-size (1024) units of a file
SYNOPSIS
sum [-o | -r] [file...]
The sum command reads file and calculates a 16-bit checksum and the byte count in block-size (1024) units in the file. If the file argu-
ment is omitted, sum reads standard input.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
sum: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
[Tru64 UNIX] Uses an algorithm to compute the checksum using word-by-word computation. Uses an alternate algorithm to compute the check-
sum (rigorous byte-by-byte computation rather than the word-by-word computation).
[Tru64 UNIX] This is the default.
OPERANDS
The file for which a checksum is to be computed. If this operand is omitted, standard input is used.
DESCRIPTION
The checksum and number of blocks are written to standard output. The sum command is generally used to determine if a file that was copied
or communicated over transmission lines is an exact copy of the original. The sum command writes the space used in 1024-byte units.
[Tru64 UNIX] The checksum is calculated using a rigorous byte-byte computation by default.
System V Compatibility
[Tru64 UNIX] The checksum algorithms for the default sum command and the SVID 2 compliant sum command are reversed. The SVID 2 compliant
sum command uses the word-by-word algorithm by default and uses the byte-by-byte algorithm if you specify the -r option on the command
line.
NOTES
The sum utility is marked LEGACY in XCU Issue 5. [Tru64 UNIX] The default algorithm is no longer the word-by-word computation algorithm.
It was changed to the 4.3BSD default algorithm. The algorithms used may not be portable, that is, the same checksum may not be produced
for the same input on different systems. Portable applications should use cksum.
EXIT STATUS
The following exit values are returned: Successful completion. An error occurred.
EXAMPLES
To display the checksum of datafile and the number of blocks in this file, enter: sum datafile
If the checksum of datafile is 1605 and if the file contains 3 blocks, sum displays: 1605 3 datafile
ENVIRONMENT VARIABLES
The following environment variables affect the execution of sum: Provides a default value for the internationalization variables that are
unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari-
ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value,
overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes
of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale for the for-
mat and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of
LC_MESSAGES.
SEE ALSO
Commands: cksum(1), wc(1)
Standards: standards(5)
sum(1)