Sponsored Content
Special Forums UNIX and Linux Applications High Performance Computing Benchmarking a Beowulf Cluster Post 302315137 by otheus on Monday 11th of May 2009 03:48:18 PM
Old 05-11-2009
Quote:
Oh the software was already installed by the university...have been told by the administrator that they are all working properly
Uh-hunh. I wouldn't completely trust that if I were you. Let's take it step-by-step.
  1. Use "type" or "which" or "whence" to find the full path of the linpack executable:
    Code:
    type -a hpl

  2. verify this has been compiled dynamically and not statically:
    Code:
    file <hpl path from step 1>

    You should see something like "Dynamically linked i386 object". As long as you don't see "statically linked binary" proceed to the next step. Otherwise, talk to your system admin and ask him/her very specifically how he/she compiled it.
  3. Next, run
    Code:
    ldd <hpl path from step 1>

    You should see something like "libopen-rte.so" in the output. If you do not, ask your sysadmin to point you to the correct hpl, the one this is compiled "against" (with) the openMPI runtimes.
  4. The libopen-rte.so should point to the full path of a file. If it does not, again, go to your system administrator and ask him/her for the full LD_LIBRARY_PATH that you should have to run against this hpl program.
  5. The path should be available to you by default on all machines in the cluster. If not, add the LD_LIBRARY_PATH setting into the .bashrc file and include your .bashrc from your .bash_profile (if you're using csh, god help you; if ksh, just change the names to .kshrc and .profile). Now log into the other machine and run the ldd command as above; you should see the line pointing to the full path of the MPI rte library.
  6. Make sure this all works by running:
    Code:
    mpirun -np 8 printenv LD_LIBRARY_PATH

    You should get 8 instances of the correct LD_LIBRARY_PATH.
  7. Now go back and try getting this to run for exactly 2 processes. (P=2, Q=1, -np 2)
  8. Now modify the machine file so it has two lines in it, one for each hostname, and run it again.
  9. If we're at this point, try again with 8; if it fails, there are some other things to look at and try.
 

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
RTLD(1) 						    BSD General Commands Manual 						   RTLD(1)

NAME
ld-elf.so.1, ld.so, rtld -- run-time link-editor DESCRIPTION
The ld-elf.so.1 utility is a self-contained shared object providing run-time support for loading and link-editing shared objects into a process' address space. It is also commonly known as the dynamic linker. It uses the data structures contained within dynamically linked programs to determine which shared libraries are needed and loads them using the mmap(2) system call. After all shared libraries have been successfully loaded, ld-elf.so.1 proceeds to resolve external references from both the main program and all objects loaded. A mechanism is provided for initialization routines to be called on a per-object basis, giving a shared object an oppor- tunity to perform any extra set-up before execution of the program proper begins. This is useful for C++ libraries that contain static con- structors. When resolving dependencies for the loaded objects, ld-elf.so.1 may be allowed to translate dynamic token strings in rpath and soname by set- ting -z origin option of the static linker ld(1). The following strings are recognized now: $ORIGIN Translated to the full path of the loaded object. $OSNAME Translated to the name of the operating system implementation. $OSREL Translated to the release level of the operating system. $PLATFORM Translated to the machine hardware platform. The ld-elf.so.1 utility itself is loaded by the kernel together with any dynamically-linked program that is to be executed. The kernel transfers control to the dynamic linker. After the dynamic linker has finished loading, relocating, and initializing the program and its required shared objects, it transfers control to the entry point of the program. The following search order is used to locate required shared objects: 1. DT_RPATH of the referencing object unless that object also contains a DT_RUNPATH tag 2. DT_RPATH of the program unless the referencing object contains a DT_RUNPATH tag 3. Path indicated by LD_LIBRARY_PATH environment variable 4. DT_RUNPATH of the referencing object 5. Hints file produced by the ldconfig(8) utility 6. The /lib and /usr/lib directories, unless the referencing object was linked using the ``-z nodefaultlib'' option The ld-elf.so.1 utility recognizes a number of environment variables that can be used to modify its behaviour. On 64-bit architectures, the linker for 32-bit objects recognizes all the environment variables listed below, but is being prefixed with LD_32_, for example: LD_32_TRACE_LOADED_OBJECTS. LD_DUMP_REL_POST If set, ld-elf.so.1 will print a table containing all relocations after symbol binding and relocation. LD_DUMP_REL_PRE If set, ld-elf.so.1 will print a table containing all relocations before symbol binding and relocation. LD_LIBMAP A library replacement list in the same format as libmap.conf(5). For convenience, the characters '=' and ',' can be used instead of a space and a newline. This variable is parsed after libmap.conf(5), and will override its entries. This variable is unset for set-user-ID and set-group-ID programs. LD_LIBMAP_DISABLE If set, disables the use of libmap.conf(5) and LD_LIBMAP. This variable is unset for set-user-ID and set-group-ID pro- grams. LD_ELF_HINTS_PATH This variable will override the default location of ``hints'' file. This variable is unset for set-user-ID and set-group- ID programs. LD_LIBRARY_PATH A colon separated list of directories, overriding the default search path for shared libraries. This variable is unset for set-user-ID and set-group-ID programs. LD_LIBRARY_PATH_RPATH If the variable is specified and has a value starting with any of 'y', 'Y' or '1' symbols, the path specified by LD_LIBRARY_PATH variable is allowed to override the path from DT_RPATH for binaries which does not contain DT_RUNPATH tag. For such binaries, when the variable LD_LIBRARY_PATH_RPATH is set, ``-z nodefaultlib'' link-time option is ignored as well. LD_PRELOAD A list of shared libraries, separated by colons and/or white space, to be linked in before any other shared libraries. If the directory is not specified then the directories specified by LD_LIBRARY_PATH will be searched first followed by the set of built-in standard directories. This variable is unset for set-user-ID and set-group-ID programs. LD_LIBRARY_PATH_FDS A colon separated list of file descriptor numbers for library directories. This is intended for use within capsicum(4) sandboxes, when global namespaces such as the filesystem are unavailable. It is consulted just after LD_LIBRARY_PATH. This variable is unset for set-user-ID and set-group-ID programs. LD_BIND_NOW When set to a nonempty string, causes ld-elf.so.1 to relocate all external function calls before starting execution of the program. Normally, function calls are bound lazily, at the first call of each function. LD_BIND_NOW increases the start- up time of a program, but it avoids run-time surprises caused by unexpectedly undefined functions. LD_TRACE_LOADED_OBJECTS When set to a nonempty string, causes ld-elf.so.1 to exit after loading the shared objects and printing a summary which includes the absolute pathnames of all objects, to standard output. LD_TRACE_LOADED_OBJECTS_ALL When set to a nonempty string, causes ld-elf.so.1 to expand the summary to indicate which objects caused each object to be loaded. LD_TRACE_LOADED_OBJECTS_FMT1 LD_TRACE_LOADED_OBJECTS_FMT2 When set, these variables are interpreted as format strings a la printf(3) to customize the trace output and are used by ldd(1)'s -f option and allows ldd(1) to be operated as a filter more conveniently. If the dependency name starts with string lib, LD_TRACE_LOADED_OBJECTS_FMT1 is used, otherwise LD_TRACE_LOADED_OBJECTS_FMT2 is used. The following conver- sions can be used: %a The main program's name (also known as ``__progname''). %A The value of the environment variable LD_TRACE_LOADED_OBJECTS_PROGNAME. Typically used to print both the names of programs and shared libraries being inspected using ldd(1). %o The library name. %p The full pathname as determined by rtld's library search rules. %x The library's load address. Additionally, ' ' and ' ' are recognized and have their usual meaning. LD_UTRACE If set, ld-elf.so.1 will log events such as the loading and unloading of shared objects via utrace(2). LD_LOADFLTR If set, ld-elf.so.1 will process the filtee dependencies of the loaded objects immediately, instead of postponing it until required. Normally, the filtees are opened at the time of the first symbol resolution from the filter object. FILES
/var/run/ld-elf.so.hints Hints file. /var/run/ld-elf32.so.hints Hints file for 32-bit binaries on 64-bit system. /etc/libmap.conf The libmap configuration file. /etc/libmap32.conf The libmap configuration file for 32-bit binaries on 64-bit system. SEE ALSO
ld(1), ldd(1), capsicum(4), elf(5), libmap.conf(5), ldconfig(8) BSD
June 20, 2014 BSD
All times are GMT -4. The time now is 05:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy