04-21-2010
Installation of MPI in a cluster of SMPs
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 (until to complete the maximum number of machines) and not on a same machine, viz :
Job A with 2 process:
Machine 1:
CPU0 Empty
CPU1 Used
Machine 2:
CPU0 Empty
CPU1 Used
but now it is scheduled as
Machine 1:
CPU0 Used
CPU1 Used
Machine 2:
CPU0 Empty
CPU1 Empty
Regards!
9 More Discussions You Might Find Interesting
1. Red Hat
Linux RedHat Cluster Manager InstallationAdministrationGuide (0 Replies)
Discussion started by: merlin
0 Replies
2. 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
3. High Performance Computing
Here are steps for installing the Solaris 10 11/06 OS, Solaris Cluster (formerly Sun Cluster) 3.2 software, QFS 4.5, and Oracle 10gR2 RAC. Also provided are instructions on how to configure QFS and Solaris Volume Manager for use with Oracle 10gR2 RAC.
More... (0 Replies)
Discussion started by: Linux Bot
0 Replies
4. High Performance Computing
Gurus,
I have several questions :
1. Does Solaris 10/OpenSolaris has some kind of web based management tools ?
Currently I am using WebMin. It worked fine, however I am very curious to use
the tools provided by Sun Microsystem.
Please advise for package name and how to activate.... (0 Replies)
Discussion started by: Zepiroth
0 Replies
5. High Performance Computing
Hai,
I am trying to install rock4.3 in my Intel core2 quad process, but when i insert kernel cd which is the first step in the installation procedure, it asks for driver disk not found.. insert CD/DVD ROM even after i inserted my CD in my driver.. could anyone help me in solving this problem...... (1 Reply)
Discussion started by: sasirekha
1 Replies
6. Solaris
While performing, solaris 10 U7 interactive initial installation I selected 'End User System Support' software group as below:
Select Software ___________________________________________________________
Select the Solaris software to install on the system.
NOTE: After selecting a software... (0 Replies)
Discussion started by: ramnagaraj
0 Replies
7. High Performance Computing
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... (1 Reply)
Discussion started by: Sonia_
1 Replies
8. Solaris
Hello.
I'm trying to install two-node Solaris cluster. All nodes has three NICs (elxl0-elxl2). elxl0 is plumbed, other interfaces - not.
At firstnode I started scinstall, made custom install, wrote hostnames of all two nodes and choose elxl1/elxl2 for cluster interconnection.
After... (1 Reply)
Discussion started by: megabyte2003
1 Replies
9. Solaris
Hi Admins,
I came across an error while installing patch cluster on solaris.
# ./installcluster --s10cluster
ERROR: Another instance of an install script is already running for target
boot
environment '/'.
I did killed the related processes. Now there is no any process running from ps... (1 Reply)
Discussion started by: snchaudhari2
1 Replies
LEARN ABOUT DEBIAN
xml::sax::machines
XML::SAX::Machines(3pm) User Contributed Perl Documentation XML::SAX::Machines(3pm)
NAME
XML::SAX::Machines - manage collections of SAX processors
SYNOPSIS
use XML::SAX::Machines qw( :all );
my $m = Pipeline(
"My::Filter1", ## My::Filter1 autoloaded in Pipeline()
"My::Filter2", ## My::Filter2 " " "
*STDOUT, ## XML::SAX::Writer also loaded
);
$m->parse_uri( $uri ); ## A parser is autoloaded via
## XML::SAX::ParserFactory if
## My::Filter1 isn't a parser.
## To import only individual machines:
use XML::SAX::Machines qw( Manifold );
## Here's a multi-pass machine that reads one document, runs
## it through 5 filtering channels (one channel at a time) and
## reassembles it in to a single document.
my $m = Manifold(
"My::TableOfContentsExtractor",
"My::AbstractExtractor",
"My::BodyFitler",
"My::EndNotesFilter",
"My::IndexFilter",
);
$m->parse_string( $doc );
DESCRIPTION
SAX machines are a way to gather and manage SAX processors without going nuts. Or at least without going completely nuts. Individual
machines can also be like SAX processors; they don't need to parse or write anything:
my $w = XML::SAX::Writer->new( Output => *STDOUT );
my $m = Pipeline( "My::Filter1", "My::Filter2", { Handler => $w } );
my $p = XML::SAX::ParserFactory->new( handler => $p );
More documentation to come; see XML::SAX::Pipeline, XML::SAX::Manifold, and XML::SAX::Machine for now.
Here are the machines this module knows about:
ByRecord Record oriented processing of documents.
L<XML::SAX::ByRecord>
Machine Generic "directed graph of SAX processors" machines.
L<XML::SAX::Machine>
Manifold Multipass document processing
L<XML::SAX::Manifold>
Pipeline A linear sequence of SAX processors
L<XML::SAX::Pipeline>
Tap An insertable pass through that examines the
events without altering them using SAX processors.
L<XML::SAX::Tap>
Config file
As mentioned in "LIMITATIONS", you might occasionally need to edit the config file to tell XML::SAX::Machine how to handle a particular SAX
processor (SAX processors use a wide variety of API conventions).
The config file is a the Perl module XML::SAX::Machines::SiteConfig, which contains a Perl data structure like:
package XML::SAX::Machines::SiteConfig;
$ProcessorClassOptions = {
"XML::Filter::Tee" => {
ConstructWithHashedOptions => 1,
},
};
So far $Processors is the only available configuration structure. It contains a list of SAX processors with known special needs.
Also, so far the only special need is the ConstructWithHashes option which tells XML::SAX::Machine to construct such classes like:
XML::Filter::Tee->new(
{ Handler => $h }
);
instead of
XML::Filter::Tee->new( Handler => $h );
WARNING If you modify anything, apply your changes in a new file created from XML::SAX::Machines::SiteConfig.pm. On Debian systems, this
should be placed in /etc/perl so that it is not overwritten during upgrade. Do not alter XML::SAX::Machines::ConfigDefaults.pm or you will
lose your changes when you upgrade.
TODO: Allow per-app and per-machine overrides of options. When needed.
AUTHORS
Barrie Slaymaker
LICENCE
Copyright 2002-2009 by Barrie Slaymaker.
This software is free. It is licensed under the same terms as Perl itself.
perl v5.10.0 2009-09-02 XML::SAX::Machines(3pm)