Sponsored Content
UNIX Standards and Benchmarks UNIX & LINUX Benchmarks (Version 3.11) UNIX Benchmarks 1024 Mb RAM / 648MHz Sparc Processor Post 46804 by mattd on Monday 26th of January 2004 10:59:32 PM
Old 01-26-2004
1024 Mb RAM / 648MHz Sparc Processor

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

BYTE UNIX Benchmarks (Version 3.11)
System -- SunOS as-1 5.8 Generic_108528-24 sun4u sparc SUNW,UltraAX-i2
Start Benchmark Run: Tue Jan 27 15:07:18 NZDT 2004
3 interactive users.
Dhrystone 2 without register variables 839082.6 lps (10 secs, 6 samples)
Dhrystone 2 using register variables 768424.1 lps (10 secs, 6 samples)
Arithmetic Test (type = arithoh) 3831540.9 lps (10 secs, 6 samples)
Arithmetic Test (type = register) 53315.1 lps (10 secs, 6 samples)
Arithmetic Test (type = short) 52631.3 lps (10 secs, 6 samples)
Arithmetic Test (type = int) 54740.7 lps (10 secs, 6 samples)
Arithmetic Test (type = long) 50915.0 lps (10 secs, 6 samples)
Arithmetic Test (type = float) 151544.7 lps (10 secs, 6 samples)
Arithmetic Test (type = double) 110019.7 lps (10 secs, 6 samples)
System Call Overhead Test 121167.1 lps (10 secs, 6 samples)
Pipe Throughput Test 71138.2 lps (10 secs, 6 samples)
Pipe-based Context Switching Test 39083.3 lps (10 secs, 6 samples)
Process Creation Test 419.8 lps (10 secs, 6 samples)
Execl Throughput Test 230.7 lps (9 secs, 6 samples)
File Read (10 seconds) 448931.0 KBps (10 secs, 6 samples)
File Write (10 seconds) 58897.0 KBps (10 secs, 6 samples)
File Copy (10 seconds) 29088.0 KBps (10 secs, 6 samples)
File Read (30 seconds) 424893.0 KBps (30 secs, 6 samples)
File Write (30 seconds) 63927.0 KBps (30 secs, 6 samples)
File Copy (30 seconds) 19336.0 KBps (30 secs, 6 samples)
C Compiler Test 22990.0 lpm (60 secs, 3 samples)
Shell scripts (1 concurrent) 314.1 lpm (60 secs, 3 samples)
Shell scripts (2 concurrent) 159.0 lpm (60 secs, 3 samples)
Shell scripts (4 concurrent) 84.6 lpm (60 secs, 3 samples)
Shell scripts (8 concurrent) 42.3 lpm (60 secs, 3 samples)
Dc: sqrt(2) to 99 decimal places 6299.2 lpm (60 secs, 6 samples)
Recursion Test--Tower of Hanoi 16921.3 lps (10 secs, 6 samples)


INDEX VALUES
TEST BASELINE RESULT INDEX

Arithmetic Test (type = double) 2541.7 110019.7 43.3
Dhrystone 2 without register variables 22366.3 839082.6 37.5
Execl Throughput Test 16.5 230.7 14.0
File Copy (30 seconds) 179.0 19336.0 108.0
Pipe-based Context Switching Test 1318.5 39083.3 29.6
Shell scripts (8 concurrent) 4.0 42.3 10.6
=========
SUM of 6 items 243.0
AVERAGE 40.5


So is this good/bad or indifferent? Smilie
mattd
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

finding out processor speeds for a sparc

i recently purchased a dual ross sparc processor kit from someone. the person listed these items as 133mhz processors, however, looking at bridgepoint's site, they do not make 133mhz processors. so i was wondering, how can i check the processor speeds? (4 Replies)
Discussion started by: xyyz
4 Replies

2. AIX

LPAR processor/virtual processor settings

Question is on setting of Physical and Virtual processors for LPARs to make proper use of virtualization capabilities. Environment is a 8-way p570 with 4 LPARs. lparVIO1 and lparVIO2: AIX 5300-04-01 Mode/Type= Shared-SMT/Capped Minimum Processors= 0.10 Desired Processors= 0.50 Maximum... (1 Reply)
Discussion started by: guttew
1 Replies

3. UNIX for Advanced & Expert Users

Are ports above 1024 closed by default ?

Hi guys, Just needed to know if all the ports above 1024 are closed by default. I know that below 1024 the ports are reserved for the kernel and ports above 1024 are reserved for user applications. But by default, if I do not have a rule in my firewall to block ports above 1024, Will my... (4 Replies)
Discussion started by: firefox211
4 Replies

4. Red Hat

red hat Linux 5.0 is detecting 3gb ram but physical ram is 16gb

Hi, On server 64bit Hw Arch , Linux 5.0(32bit) is installed it is showing only 3gb of ram though physical is 16gb can u give me idea why? (4 Replies)
Discussion started by: manoj.solaris
4 Replies

5. Linux Benchmarks

AMD Phenom(tm) 9950 Quad-Core Processor, Ram: 3.6 GB, Foxconn 7da-s and Linux 2.6.26-2-amd64

CPU/Speed: AMD Phenom(tm) 9950 Quad-Core Processor Ram: 3.6 GB Motherboard: Foxconn 7da-s Bus: Cache: Controller: Disk: Load: Kernel: Linux 2.6.26-2-amd64 Kernel ELF?: pgms: ============================================================== BYTE UNIX Benchmarks (Version... (0 Replies)
Discussion started by: migracho
0 Replies

6. Red Hat

ssh_host_rsa_key 1024 bit?

Hi All, How do I know if ssh_host_rsa_key is 1024 bit? cat /etc/ssh/ssh_host_rsa_key | wc -m 887 It's only 887. Is that it? Or not? Thank you for any comment you may add. (2 Replies)
Discussion started by: itik
2 Replies

7. UNIX for Dummies Questions & Answers

RSA 1024

How to generate RSA 1024 public key?? Pls help (3 Replies)
Discussion started by: kdtrica
3 Replies

8. Shell Programming and Scripting

1024 field issue : awk

Hi i have a txt file in which i do a awk operation with ":" as field separator A B C D ABC::2386.13:2386.13:3248234281995::+DPY:INT:3:N::::2:200.00:0.00:2010-05-12:CA: ::2:N::N:PH:00010031:0001+DPY:BAL:3:N::::3:1601.01:0.00:2010-05-12:XT::2:N:MR ... (1 Reply)
Discussion started by: mad_man12
1 Replies
platform(4)							   File Formats 						       platform(4)

NAME
platform - directory of files specifying supported platforms SYNOPSIS
.platform DESCRIPTION
The Solaris operating environment release includes the .platform directory, a new directory on the Solaris CD image. This directory con- tains files (created by Sun and Solaris OEMs) that define platform support. These files are generically referred to as platform definition files. They provide a means to map different platform types into a platform group. Platform definition files in the .platform directory are used by the installation software to ensure that software appropriate for the architecture of the system will be installed. Sun provides a platform definition file named .platform/Solaris . This file is the only one that can define platform groups to which other platform definition files can refer. For example, an OEM platform definition file can refer to any platform group specified in the Solaris platform definition file. Other platform definition files are delivered by OEMs. To avoid name conflicts, OEMs will name their platform definition file with an OEM- unique string. OEMs should use whatever string they use to make their package names unique. This unique string is often the OEM's stock symbol. Comments are allowed in a platform definition file. A "#" begins a comment and can be placed anywhere on a line. Platform definition files are composed of keyword-value pairs, and there are two kinds of stanzas in the file: platform group definitions and platform identifications. o Platform group definitions: The keywords in a platform group definition stanza are: PLATFORM_GROUP The PLATFORM_GROUP keyword must be the first keyword in the platform group definition stanza. The value assigned to this keyword is the name of the platform group, for example: PLATFORM_GROUP=sun4c The PLATFORM_GROUP name is an arbitrary name assigned to a group of platforms. However, PLATFORM_GROUP typically equals the output of the uname -m command. PLATFORM_GROUP value cannot have white space and is limited to 256 ASCII characters. INST_ARCH The instruction set architecture of all platforms in the platform group, for example: INST_ARCH=sparc The INST_ARCH keyword value must be the value returned by the uname -p command on all platforms in the platform group. o Platform identifications: The keywords in a platform identification stanza are: PLATFORM_NAME The PLATFORM_NAME keyword must be the first keyword in the platform identification stanza. The PLATFORM_NAME is the name assigned to the platform, for example: PLATFORM_NAME=SUNW,SPARCstation-5 Typically, this name is the same as the value returned by the uname -icommand on the machine, but it need not be the same. The PLATFORM_NAME value cannot have white space and is limited to 256 ASCII characters. If it contains paren- theses, it must contain only balanced parentheses. For example. the string "foo(bar)foo" is a valid value for this keyword, but "foo(bar" is not. The other keywords in the platform identification stanza can be in any order, as long as the PLATFORM_NAME keyword is first. PLATFORM_ID The value returned by the uname -i command on the machine, for example: PLATFORM_ID=SUNW,SPARCstation-5 MACHINE_TYPE The value returned by the uname -m command on the machine, for example: MACHINE_TYPE=sun4c IN_PLATFORM_GROUP The platform group of which the platform is a member, for example: IN_PLATFORM_GROUP=sun4c The platform group name must be specified in the same file as the platform identification stanza or in the platform definition file with the name .platform/Solaris . The IN_PLATFORM_GROUP keyword is optional. A platform doesn't have to belong to a platform group. If a plat- form is not explicitly assigned to a platform group, it essentially forms its own platform group, where the platform group name is the PLATFORM_NAME value. The IN_PLATFORM_GROUP value typically equals the output of the uname -m command. IN_PLATFORM_GROUP value cannot have white space and is limited to 256 ASCII characters. INST_ARCH The instruction set architecture of the platform, for example: INST_ARCH=sparc This field is only required if the platform does not belong to a platform group. The INST_ARCH keyword value must be the value returned by the uname -i command on all platforms in the platform group. COMPATIBILITY
The installation program will remain compatible with the old Solaris CD format. If a Solaris CD image does not contain any platform defini- tion files, the installation and upgrade programs will select the packages to be installed based on machine type, that is, the value returned by the uname -p command. EXAMPLES
Example 1: Platform Group Definitions The following example shows platform group definitions from the .platform/Solaris platform definition file. # PLATFORM_GROUP=sun4u INST_ARCH=sparc Example 2: Platform Identification Stanzas The following example shows platform identification stanzas, which define systems that belong in a platform group, from the .plat- form/Solaris platform definition file. # PLATFORM_NAME=SUNW,SunFire PLATFORM_ID=SUNW,SunFire IN_PLATFORM_GROUP=sun4u PLATFORM_NAME=SUNW,Ultra-80 PLATFORM_ID=SUNW,Ultra-80 IN_PLATFORM_GROUP=sun4u # PLATFORM_NAME=SUNW,SunFire PLATFORM_ID=SUNW,SunFire IN_PLATFORM_GROUP=sun4u # PLATFORM_NAME=SUNW,Ultra-80 PLATFORM_ID=SUNW,Ultra-80 IN_PLATFORM_GROUP=sun4u FILES
The .platform directory must reside as /cd_image/Solaris_vers/.platform, where cd_image Is the path to the mounted Solaris CD (/cdrom/cdrom0/s0 by default) or the path to a copy of the Solaris CD on a disk. Solaris_vers Is the version of Solaris, for example, Solaris_2.9. NOTES
Typically, a platform identification stanza contains either a PLATFORM_ID or a MACHINE_TYPE stanza, but not both. If both are specified, both must match for a platform to be identified as this platform type. Each platform identification stanza must con- tain either a PLATFORM_ID value or a MACHINE_TYPE value. If a platform matches two different platform identification stanzas--one which matched on the value of PLATFORM_ID and one which matched on the value of MACHINE_TYPE , the one that matched on PLATFORM_ID will take precedence. The .platform directory is part of the Solaris CD image, whether that be the Solaris CD or a copy of the Solaris CD on a system's hard disk. SunOS 5.10 19 Nov 2002 platform(4)
All times are GMT -4. The time now is 05:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy