Sponsored Content
Special Forums UNIX and Linux Applications High Performance Computing Benchmarking a Beowulf Cluster Post 302314323 by otheus on Friday 8th of May 2009 04:27:08 AM
Old 05-08-2009
Quote:
That is trying to run it on 8 cores across 2 nodes. I have also tried your HPL.dat you provided, and i get a similar error except it says Need at least 12 processes.

Do you know what causes these errors. I have a hosts file in the same directory with the names of the two nodes which i wish to run the tests on.

At the command line i am typing:

mpirun -np 8 -machinefile hosts xhpl_em64t

where hosts file has the names:
machine1
machine2
Several points:
  • The number of processor-cores you run this thing on must match the product of P and Q. So if P is 2 and Q is 4, you will need 8 cores; no more, no less
  • If you provide MPICH with -np 8 and you specify a machine file, it expects at least that number of hosts in the machine file. If a host has multiple processor-cores (in your case, yes of course), you enter the hostname for each core. So if machine1 has 8 processor cores, your machinefile should include 8 lines of "machine1".
 

9 More Discussions You Might Find Interesting

1. UNIX Benchmarks

Server and Workstation benchmarking

This is from my server AMD K6 133MHz 64Mb RAM 4GB HDD (Maxtor - ATA33) 2x10Mb NIC 1Mb Intel Graphic Card BYTE UNIX Benchmarks (Version 3.11) System -- FreeBSD sergiu.tarnita.net 5.0-RELEASE FreeBSD 5.0-RELEASE #2: Thu Mar 17 15:49:16 EET 2005... (0 Replies)
Discussion started by: Sergiu-IT
0 Replies

2. HP-UX

HP-Unix Hardware benchmarking

Hi everyone, I'm working on one HP-Unix application which we have to port completely onto Windows xp. Before that I have to compare performance of two different machines. My HP-Unix is running on HP-C8000 workstation and windows XP machine is intel Xeon. Now the problem is to evaluate the... (0 Replies)
Discussion started by: dgatkal
0 Replies

3. High Performance Computing

Building a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris

Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris. More... (0 Replies)
Discussion started by: Linux Bot
0 Replies

4. High Performance Computing

MySQL Cluster - Designing, Evaluating and Benchmarking (reg. req'd)

Registration is required. In this white paper learn the fundamentals of how to design and select the proper components for a successful MySQL Cluster evaluation. Explore hardware, networking and software requirements. Work through basic functional testing and evaluation best practices. More... (0 Replies)
Discussion started by: Linux Bot
0 Replies

5. High Performance Computing

Tuning HPL.dat for Beowulf Cluster [Linpack]

Hi guys, I am having some issues tuning the HPL.dat file for the Linpack benchmark test across 2 nodes. I am very new to this with minimal Linux experience, however i am trying my luck. The specs for the two nodes are: 3GHZ QX6850 CORE 2 EXTREME (QUAD CORE) 4GB RAM I have been typing these... (1 Reply)
Discussion started by: mercthunder
1 Replies

6. UNIX for Advanced & Expert Users

Benchmarking a new Solaris, with four different clients

Good morning, for the impatient: I have a new backup-server and need to monitor, what the machine can do, what's the best way of finding that out? I will tell the story right from the beginning, so you have a clue about what's going on: I have a setup of three machines: A new... (6 Replies)
Discussion started by: PatrickBaer
6 Replies

7. UNIX for Dummies Questions & Answers

benchmarking application

Where i get a open source benchmark program using pthread library for benchmarking our multicore system for the first stage.I need the source code too for that application ,because in later stage we need to develop our application so that i need to study pthread more. please anybody guide me . (0 Replies)
Discussion started by: sujith4u87
0 Replies

8. UNIX and Linux Applications

Benchmarking and performance analyzing in OS

Is/Are there an/some application/applications , package/packages for benchmarking or system performance measuring which are there for almost all Linux releases and distributions? (2 Replies)
Discussion started by: nixhead
2 Replies

9. Solaris

Sun cluster 4.0 - zone cluster failover doubt

Hello experts - I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts. (1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over) (2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies
pset_ctl(2)							System Calls Manual						       pset_ctl(2)

NAME
pset_ctl() - processor set control SYNOPSIS
DESCRIPTION
The function provides a means to query the system processor set configuration and assignment information. The request argument specifies what information is needed for the pset processor set. The following request values are supported: Return the ID of the processor set binding for the calling thread. The pset and id arguments are ignored. Return the ID of the first locality domain contributing to the processor set pset. The id argument is ignored. Return the ID of the first processor in the processor set pset that is in the proximity of the processor specified by id. Even when the processor given by id is enabled, the return value will be -1 if none of the proximate processors contribute to the processor set pset. If the processor given by id is not enabled, -1 is returned. See mpctl(2) for details on proximate processors. Return the ID of the first processor set in the system. The pset and id arguments are ignored. Return the ID of the first processor in the processor set pset. It will return -1 if the processor set is empty. Any processors in the processor set that is in transition are ignored. The id argument is ignored. Return the ID of the next locality domain after the locality domain specified in id that contributes to the processor set pset. Typically, is called to determine the first locality domain in a processor set. is then called in a loop (until the call returns -1) to determine the IDs of the remaining locality domain in the processor set. Return the ID of the next processor in the processor set pset that is in the proximity of the processor specified by id. Typically, is called to determine the first proximate processor. is then called in a loop (until the call returns -1) to deter- mine the IDs of the remaining proximate processors. Return the ID of the next processor set in the system after pset. The id argument is ignored. Typically, is called to determine the first processor set. is then called in a loop (until the call returns -1) to determine the IDs of the remaining processor sets in the system. Return the ID of next processor in the processor set pset after the processor specified in id. Typically, is called to determine the first processor in a processor set. is then called in a loop (until the call returns -1) to determine the IDs of the remaining processors in the processor set. Return the number of locality domains that have at least one processor assigned to the processor set pset. The id argument is ignored. Return the number of processors assigned to the processor set pset that are in the proximity of the processor specified by id. Even when the processor given by id is enabled, the return value will be 0 if none of proximate processors contribute to the processor set pset. If the processor given by id is not enabled, -1 is returned. Return the current number of processor sets in the system. It will always be greater than or equal to one. The pset and id arguments are ignored. Return the number of processors assigned to the processor set pset. Any processors in the processor set that is in transition are not included. The id argument is ignored. Return number of processors contributed by the locality domain specified by id to the processor set pset. Return the ID of the processor set assigned for the processor specified in id. If the processor is not enabled or is in transition from one processor set to another, -1 is returned with an error. The pset argument is ignored. Logical Processor and Processor Core Information On systems with the Hyper-Threading (HT) feature enabled, each processor core may have more than one hyper-thread per physical processor core. When hyper-threading is enabled at the firmware level, each hyper-thread is represented to the operating system and applications as a logical processor (LCPU). Hence the basic unit of any topology information is a logical processor. However, some applications may want to get the system topology information at the physical processor core level. Returns the number of processor cores assigned to the processor set pset. Any processor cores in the processor set that are in transition are not included. The id argument is ignored. Returns the ID of the first processor core in the processor set pset. It will return -1 if the processor set is empty. Any processor cores in the processor set that is in transition are ignored. The id argument is ignored. Returns the ID of the next processor core in the processor set pset after the processor specified in id. Typically, is called to determine the first processor core in a processor set. is then called in a loop (until the call returns -1) to determine the IDs of remaining processor cores in the processor set. Returns the number of enabled processor cores assigned to the processor set pset. Any user may query the system processor set topology using the function. Use with name to see if the processor set functionality is supported by the underlying HP-UX operating system version. RETURN VALUE
returns a value based on on successful completion. Success. The value is based on the request. Failure. is set to indicate the error. ERRORS
sets to one of the following values if the corresponding condition is detected. The request is invalid. The specified processor set pset, or the processor or the locality domain specified by id is invalid. The request is and there is no other processor set after pset, or the request is and there is no other processor after id in pset, or the request is and there is no other locality domain after id in pset, or the request is and there is no other proxi- mate processor after id in pset. The request is or and the processor specified by id is not enabled. The processor set functionality is not supported by the underlying HP-UX version. EXAMPLES
Get total count and IDs of all processor sets in the system. AUTHOR
was developed by HP. SEE ALSO
psrset(1M), mpctl(2), pset_assign(2), pset_bind(2), pset_create(2), pset_destroy(2), pset_getattr(2), pset_setattr(2), sysconf(2), privi- leges(5). pset_ctl(2)
All times are GMT -4. The time now is 05:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy