HPC Linpack test


 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications High Performance Computing HPC Linpack test
Prev   Next
# 3  
Old 10-06-2012
I expected the name of the library that I can use -
from the people who worked with hpl. If you do not know it, do not write.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Homework & Coursework Questions

Class hpc project

My high school started a tech lab where students like myself can take apart computers, build circuit boards, learn to program and lots more. I got the job of building a cluster with 4 old work stations we have. This is just a trial if it works well we can get more work stations. We have one... (3 Replies)
Discussion started by: PC-2011
3 Replies

2. High Performance Computing

High Performance Linpack Compiling Issue

I'm trying to compile Linpack on a Ubuntu cluster. I'm running MPI. I've modified the following values to fit my system TOPdir MPdir LAlib CC LINKER. When compiling I get the following error: (the error is at the end, the other errors in between are because I've ran the script several times so... (0 Replies)
Discussion started by: JPJPJPJP
0 Replies

3. High Performance Computing

Guides for new HPC admins

In my company, it's fallen on me to serve as the admin of our new HPC cluster, a task that's very new to me. It's very important to me to lay a solid foundation and avoid any unnecessary pitfalls. So, can anyone recommend a succinct guide or list of do's-and-don'ts for adiminstering an HPC cluster?... (0 Replies)
Discussion started by: DBryan
0 Replies

4. Shell Programming and Scripting

How to check weather a string is like test* or test* ot *test* in if condition

How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies

5. Shell Programming and Scripting

Test on string containing spacewhile test 1 -eq 1 do read a $a if test $a = quitC then break fi d

This is the code: while test 1 -eq 1 do read a $a if test $a = stop then break fi done I read a command on every loop an execute it. I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test. For example echo hello. Now the... (1 Reply)
Discussion started by: Max89
1 Replies

6. 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

7. High Performance Computing

HPC Related Links

Our directory of HPC related links is growing: Virtualization, Grid and Cloud Computing - Links Please contribute! (0 Replies)
Discussion started by: Neo
0 Replies

8. Linux Benchmarks

Conversion to Linpack

Should we conver to Linpack for Linux Benchmarks? http://www.netlib.org/benchmark/hpl/ What do you think? (0 Replies)
Discussion started by: Neo
0 Replies
Login or Register to Ask a Question
GTESTER(1)							   User Commands							GTESTER(1)

NAME
gtester - test running utility SYNOPSIS
gtester [OPTION...] [testprogram] DESCRIPTION
gtester is a utility to run unit tests that have been written using the GLib test framework. When called with the -o option, gtester writes an XML report of the test results, which can be converted into HTML using the gtester-report utility. OPTIONS
-h, --help print help and exit -v, --version print version information and exit --g-fatal-warnings make warnings fatal -k, --keep-going continue running after tests failed -l list paths of available test cases -m=MODE run test cases in MODE, which can be one of: perf run performance tests slow, thorough run slow tests, or repeat non-deterministic tests more often quick do not run slow or performance tests, or do extra repeats of non-deterministic tests (default) undefined run test cases that deliberately provoke checks or assertion failures, if implemented (default) no-undefined do not run test cases that deliberately provoke checks or assertion failures -p=TESTPATH only run test cases matching TESTPATH -s=TESTPATH skip test cases matching TESTPATH --seed=SEEDSTRING run all test cases with random number seed SEEDSTRING -o=LOGFILE write the test log to LOGFILE -q, --quiet suppress per test binary output --verbose report success per testcase SEE ALSO
gtester-report(1) GLib GTESTER(1)