Sponsored Content
Special Forums UNIX and Linux Applications High Performance Computing IBM Hardware: Test speed of an execution core reliably. Post 302852907 by Corona688 on Thursday 12th of September 2013 03:12:05 PM
Old 09-12-2013
Multithreading does not work that way; two cores can't cooperate to run a single-threaded program faster. Single-threaded programs will run slower on machines with lots of slower cores; we've had some puzzled folks ask us why their new machines have worse single-threaded benchmarks than their old ones.

But more cores means you can run more threads or processes at once without sharing time; more total work can be accomplished in the aggregate; but a program has to be designed with this in mind (or multiple instances of it run) to take advantage of this capability.
 

8 More Discussions You Might Find Interesting

1. AIX

FTP Speed Problem on IBM P-Series equiped with AIX 5.2

Hi, We have IBM P-Series servers (P690, P650) equiped with AIX 5.2. Further we have 10/100 MB ethernet cards in P650 and 10/100/1000 MB ethernet cards in P690 servers. Servers are on a LAN connected with Cisco 3750 catalyst switch. FTP from one server to another is very slow,,,even 3-4 MB... (3 Replies)
Discussion started by: aqeelcu@hotmail
3 Replies

2. AIX

IBM Hardware question

I am looking to buy a 7044 - either a 170 or 270. From what I can find on web searchs the 170 is NOT upgradable to more that one CPU? Is that correct? Can I upgrade the planer on a 170 to a 270 to support multiple CPU's? Does anyone have any other suggestion for AIX hardware? (5 Replies)
Discussion started by: dizman67
5 Replies

3. UNIX for Advanced & Expert Users

speed test +20,000 file existance checks too slow

Need to make a very fast file existence checker. Passing in 20-50K num of files In the code below ${file} is a file with a listing of +20,000 files. test_speed is the script. I am commenting out the results of <time test_speed try>. The normal "test -f" is much much too slow when a system... (2 Replies)
Discussion started by: nullwhat
2 Replies

4. AIX

core dump generation in IBM machine

Hi, im getting a core dump file in a AIX machine while using a complex c++ program. The same program is working without any core error in another system with sun OS 5.9. The program has used structs, LL's and lots of call by references. What may be the reason. will it be a problem with the OS ? (3 Replies)
Discussion started by: suresh_kb211
3 Replies

5. Solaris

hardware test fails

Hi, I have a SunFire 280R abd when I boot it there is a hardware check running and it fails. Here is a long output of the test rsc> poweron Are you sure you want to turn your system power on (Yes/No)? yes rsc> console RSC Alert: Host System has Reset @(#)OBP 4.5.10 2002/02/11 10:39... (2 Replies)
Discussion started by: Tex-Twil
2 Replies

6. Hardware

Hardware Correction: How to change DVD write speed

I am now on Kernel 2.6.32-26 For me 16x CD write speed is okay. I have old hardware which was able to write DVDs at 1x, back in previous linux version. Now, I dont get speed of less than 4x. Tested on k3b, xfburn, and brasero. But all start at bottom 4x write speed. k3b forced back to... (0 Replies)
Discussion started by: makh
0 Replies

7. AIX

New to AIX and IBM Hardware. Need some info

Hello all. I'm new to AIX and IBM hardware and I have a question around the configuration of the service processor on the power series. I need to know: 1) How do I get into the service processor from the serial console when AIX is up and running. I come from the Sun world and I tried all I know.... (1 Reply)
Discussion started by: glenc2004
1 Replies

8. Hardware

How to test the speed of your WIFI network?

Dear all, Would you know how to measure the max speed of a WIFI connection between a router and a laptop for instance? Many thanks for your help! Regards, (3 Replies)
Discussion started by: freddie50
3 Replies
yade-batch(1)						      General Commands Manual						     yade-batch(1)

NAME
yade-batch - batch system for computational platform Yade SYNOPSIS
yade-batch [options] [ TABLE [SIMULATION.py] | SIMULATION.py[/nCores] [...] ] DESCRIPTION
yade-batch Manage batches of computation jobs for the Yade platform; batches are described using text-file tables with parameters which are passed to individual runs of yade. Jobs are being run with pre-defined number of computational cores as soon as the required number of cores is available. Logs of all computations are stored in files and the batch progress can be watched online at (usually) http://local- host:9080. Unless overridden, the executable yade is used to run jobs. OPTIONS
--help, -h show this help message and exit --jobs=NUM, -j NUM Maximum number of simultaneous threads to run (default: number of cores, further limited by OMP_NUM_THREADS if set by the environ- ment: 4) --job-threads=NUM Default number of threads for one job; can be overridden by per-job with !THREADS (or !OMP_NUM_THREADS) column. Defaults to 1. --force-threads Force jobs to not use more cores than the maximum (see -j), even if !THREADS colums specifies more. --log=FORMAT Format of job log files: must contain a $, % or @, which will be replaced by script name, line number or by description column respectively (default: $.@.log) --global-log=FILE Filename where to redirect output of yade-batch itself (as opposed to --log); if not specified (default), stdout/stderr are used --lines=LIST, -l LIST Lines of TABLE to use, in the format 2,3-5,8,11-13 (default: all available lines in TABLE) --nice=NICE Nice value of spawned jobs (default: 10) --cpu-affinity Bind each job to specific CPU cores; cores are assigned in a quasi-random order, depending on availability at the moment the jobs is started. Each job can override this setting by setting AFFINE column. --executable=FILE Name of the program to run (default: /tmp/buildd/yade-0.80.1/debian/inst/bin/yade). Jobs can override with !EXEC column. --rebuild Run executable(s) with --rebuild prior to running any jobs. --debug Run the executable with --debug. Can be overriddenn per-job with !DEBUG column. --gnuplot=FILE Gnuplot file where gnuplot from all jobs should be put together --dry-run Do not actually run (useful for getting gnuplot only, for instance) --http-wait Do not quit if still serving overview over http repeatedly --generate-manpage=FILE Generate man page documenting this program and exit --plot-update=TIME Interval (in seconds) at which job plots will be updated even if not requested via HTTP. Non-positive values will make the plots not being updated and saved unless requested via HTTP (see --plot-timeout for controlling maximum age of those). Plots are saved at exit under the same name as the log file, with the .log extension removed. (default: 120 seconds) --plot-timeout=TIME Maximum age (in seconds) of plots served over HTTP; they will be updated if they are older. (default: 30 seconds) --refresh=TIME Refresh rate of automatically reloaded web pages (summary, logs, ...). --timing=COUNT Repeat each job COUNT times, and output a simple table with average/variance/minimum/maximum job duration; used for measuring how various parameters affect execution time. Jobs can override the global value with the !COUNT column. --timing-output=FILE With --timing, save measured durations to FILE, instead of writing to standard output. --randomize Randomize job order (within constraints given by assigned cores). SEE ALSO
yade (1) https://yade-dem.org/sphinx/user.html#batch-queuing-and-execution-yade-batch COPYRIGHT
(C) 2003--2012 Yade Developers Team This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY 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 this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA. BUGS
Please report bugs to the project's bug tracker at http://bugs.launchpad.net/yade AUTHOR
Yade Developers Team (http://www.launchpad.net/~yade-dev) yade-batch 2012-7-4 yade-batch(1)
All times are GMT -4. The time now is 03:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy