Sponsored Content
Full Discussion: HPC Linpack test
Special Forums UNIX and Linux Applications High Performance Computing HPC Linpack test Post 302711225 by DGPickett on Friday 5th of October 2012 02:14:30 PM
 

8 More Discussions You Might Find Interesting

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

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

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

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

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

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

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

8. 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
MYSQL-STRESS-TE(1)					       MySQL Database System						MYSQL-STRESS-TE(1)

NAME
mysql-stress-test.pl - server stress test program SYNOPSIS
mysql-stress-test.pl [options] DESCRIPTION
The mysql-stress-test.pl Perl script performs stress-testing of the MySQL server. (MySQL 5.0 and up only) mysql-stress-test.pl requires a version of Perl that has been built with threads support. Invoke mysql-stress-test.pl like this: shell> mysql-stress-test.pl [options] mysql-stress-test.pl supports the following options: o --help Display a help message and exit. o --abort-on-error=N Causes the program to abort if an error with severity less than or equal to N was encountered. Set to 1 to abort on any error. o --check-tests-file Periodically check the file that lists the tests to be run. If it has been modified, reread the file. This can be useful if you update the list of tests to be run during a stress test. o --cleanup Force cleanup of the working directory. o --log-error-details Log error details in the global error log file. o --loop-count=N In sequential test mode, the number of loops to execute before exiting. o --mysqltest=path The path name to the mysqltest program. o --server-database=db_name The database to use for the tests. The default is test. o --server-host=host_name The host name of the local host to use for making a TCP/IP connection to the local server. By default, the connection is made to localhost using a Unix socket file. o --server-logs-dir=path This option is required. path is the directory where all client session logs will be stored. Usually this is the shared directory that is associated with the server used for testing. o --server-password=password The password to use when connecting to the server. o --server-port=port_num The TCP/IP port number to use for connecting to the server. The default is 3306. o --server-socket=file_name For connections to localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use. The default if /tmp/mysql.sock. o --server-user=user_name The MySQL user name to use when connecting to the server. The default is root. o --sleep-time=N The delay in seconds between test executions. o --stress-basedir=path This option is required. path is the working directory for the test run. It is used as the temporary location for result tracking during testing. o --stress-datadir=path The directory of data files to be used during testing. The default location is the data directory under the location given by the --stress-suite-basedir option. o --stress-init-file[=path] file_name is the location of the file that contains the list of tests to be run once to initialize the database for the testing. If missing, the default file is stress_init.txt in the test suite directory. o --stress-mode=mode This option indicates the test order in stress-test mode. The mode value is either random to select tests in random order or seq to run tests in each thread in the order specified in the test list file. The default mode is random. o --stress-suite-basedir=path This option is required. path is the directory that has the t and r subdirectories containing the test case and result files. This directory is also the default location of the stress-test.txt file that contains the list of tests. (A different location can be specified with the --stress-tests-file option.) o --stress-tests-file[=file_name] Use this option to run the stress tests. file_name is the location of the file that contains the list of tests. If file_name is omitted, the default file is stress-test.txt in the stress suite directory. (See --stress-suite-basedir.) o --suite=suite_name Run the named test suite. The default name is main (the regular test suite located in the mysql-test directory). o --test-count=N The number of tests to execute before exiting. o --test-duration=N The duration of stress testing in seconds. o --threads=N The number of threads. The default is 1. o --verbose Verbose mode. Print more information about what the program does. COPYRIGHT
Copyright (C) 2006, 2013, Oracle and/or its affiliates. All rights reserved. This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License. This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/. SEE ALSO
For more information, please refer to the MySQL Reference Manual, which may already be installed locally and which is also available online at http://dev.mysql.com/doc/. AUTHOR
Oracle Corporation (http://dev.mysql.com/). MySQL 01/23/2014 MYSQL-STRESS-TE(1)
All times are GMT -4. The time now is 01:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy