04-21-2010
MPI + Cluster SMP
Hola, he instalado mpich2 vs. 1.2.1p1 en un cluster de biprocesadores con las opciones por defecto (antes usaba ssm pero visto que se quedaba colgado, lo he dejado con nemesis).
El caso es que quisiera que cada vez que lanzo un job (por ejemplo de 2 procesos), cada proceso del trabajo se fuera ejecutando en una máquina diferente (hasta llegar al número máximo de máquinas) y no en la misma máquina. Es decir:
Trabajo A en 2 procesos:
Máquina 1:
CPU0 Ocupada
CPU1 No Ocupada
Máquina 2:
CPU0 Ocupada
CPU1 No Ocupada
Un saludin
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
What is the SMP support like when you are running Linux 7.3 on a system with 2-4 CPUs? (3 Replies)
Discussion started by: AngryRabbi
3 Replies
2. SCO
I have a dell machine Dell 2600 PowerEdge it has two processor (intel Xeon ).
Is there a path or a software that will work with SCO unix in order to enable second processor and how would i know that the second processor is active.
Thanks a lot guys . (1 Reply)
Discussion started by: josramon
1 Replies
3. Linux Benchmarks
System:
CPU/Speed: Dual Intel Xeon 2.4Ghz
Ram: 2 GB DDR 266 SDRAM
Motherboard: SuperMicro X5DE8-GG
Bus: 533MHz/400MHz system bus -
Cache: 512KB
HD Controller: EIDE Serverworks™ GC-SL Chipset
Extra GCC compiler flags:
-s... (3 Replies)
Discussion started by: Neo
3 Replies
4. Red Hat
I have installed redhat linux 9.0 on P4 HT machine. The grub boot loader shows path to smp mode and normal mode. when machine shut downs from smp version kernal , need to press the power button to power off. But in normal mode the system shut downs or power downs automatically(ie, full... (2 Replies)
Discussion started by: pcsaji
2 Replies
5. Programming
Interesting issue. There was some discussion on the LKML last year regarding the potential problems in concurrent applications reusing file descriptors in various scenarios. The main issue is that the reuse of a file descriptor and reception of data in a threaded application can be confused pretty... (1 Reply)
Discussion started by: ramen_noodle
1 Replies
6. UNIX for Dummies Questions & Answers
hi, may i know how to run mpi after i had install the rock cluster? is there any guidelines or examples? (0 Replies)
Discussion started by: joannetan9984
0 Replies
7. High Performance Computing
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
8. High Performance Computing
Hi,
I've installed mpich2 v. 1.2.1p1 on a cluster of dual-processors with the default options (in previous versions I used 'ssm' device, but now I use 'nemesis').
I'd like that every time I execute a job (e.g. with 2 MPI-processes), each job's process be dispatched on a different machine... (0 Replies)
Discussion started by: Sonia_
0 Replies
9. Solaris
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
10. Programming
The SCO OSR 5.7 system was migrated from older HP DL360 to new DL380 G7. The SMP feature was not activated on older box, it is activated now on this 4 core Xeon.
A s/w we maintain has been copied without any change over to the new box. I noticed that the application profiling does not show any... (4 Replies)
Discussion started by: migurus
4 Replies
LEARN ABOUT DEBIAN
svsematest
svsematest(8) svsematest(8)
NAME
svsematest - Start two threads or fork two processes and measure the latency of SYSV semaphores
SYNTAX
svsematest [-a|-a PROC] [-b USEC] [-d DIST] [-f] [-i INTV] [-l loops] [-p PRIO] [-t|-t NUM]
DESCRIPTION
The program svsematest starts two threads or, optionally, forks two processes that are synchronized via SYSV semaphores and measures the
latency between releasing a semaphore on one side and getting it on the other side.
OPTIONS
-a, --affinity[=PROC]
Run on procesor number PROC. If PROC is not specified, run on current processor.
-b, --breaktrace=USEC
Send break trace command when latency > USEC. This is a debugging option to control the latency tracer in the realtime preemption
patch. It is useful to track down unexpected large latencies of a system.
-d, --distance=DIST
Set the distance of thread intervals in microseconds (default is 500 us). When cylictest is called with the -t option and more than
one thread is created, then this distance value is added to the interval of the threads: Interval(thread N) = Interval(thread N-1) +
DIST
-f, --fork
Instead of creating threads (which is the default), fork new processes
-i, --interval=INTV
Set the base interval of the thread(s) in microseconds (default is 1000 us). This sets the interval of the first thread. See also
-d.
-l, --loops=LOOPS
Set the number of loops. The default is 0 (endless). This option is useful for automated tests with a given number of test cycles.
svsematest is stopped once the number of timer intervals has been reached.
-p, --prio=PRIO
Set the priority of the process.
-t, --threads[=NUM]
Set the number of test threads (default is 1, if this option is not given). If NUM is specified, create NUM test threads. If NUM is
not specifed, NUM is set to the number of available CPUs.
EXAMPLES
The following example was running on a 4-way CPU:
# svsematest -a -t -p99 -i100 -d25 -l1000000
#0: ID13110, P99, CPU0, I100; #1: ID13111, P99, CPU0, Cycles 1000000
#2: ID13112, P98, CPU1, I125; #3: ID13113, P98, CPU1, Cycles 813573
#4: ID13114, P97, CPU2, I150; #5: ID13115, P97, CPU2, Cycles 667285
#6: ID13116, P96, CPU3, I175; #7: ID13117, P96, CPU3, Cycles 591403
#1 -> #0, Min 1, Cur 2, Avg 2, Max 12
#3 -> #2, Min 1, Cur 3, Avg 2, Max 12
#5 -> #4, Min 1, Cur 3, Avg 3, Max 12
#7 -> #6, Min 1, Cur 2, Avg 3, Max 11
AUTHORS
Carsten Emde <C.Emde@osadl.org>
SEE ALSO
semop(2)
0.1 svsematest(8)