>> I attach a patch, but it doesn't work and I don't see where the
>> error lies now. It may be that I'm doing something stupid.
>> It produces working OpenMPI-1.3.4 package on Dragonfly though.
>
> Ok, I'll try and merge it in to the working stuff we have here.
> I, obviously, just #ifdef'd for N
Hi Matthew
Please see comments/answers inline below.
Matthew MacManes wrote:
Hi Gus,
Thanks for your ideas.. I have a few questions, and will try to answer
yours in hopes of solving this!!
A simple way to test OpenMPI on your system is to run the
test programs that come with the OpenMPI sou
OK, it works although there are some temporary errors.
This is the NetBSD wip openmpi package as downloaded from the
webCVS a couple of days ago but with my patches as detailed
before (I have not tried comparing yours with mine as yet)
and the removal of the compilation and install of the Vampire
Hi Gus,
Thanks for your ideas.. I have a few questions, and will try to answer yours in
hopes of solving this!!
Should I worry about setting things like --num-cores --bind-to-cores? This, I
think, gets at your questions about processor affinity.. Am I right? I could
not exactly figure out th
Gus Correa wrote:
Hi Matthew
5) Are you setting processor affinity on mpiexec?
mpiexec -mca mpi_paffinity_alone 1 -np ... bla, bla ...
Good point. This option optimizes processor affinity on the assumption
that no other jobs are running. If you ran 2 MPI jobs with this option,
they wou
The Open MPI Team, representing a consortium of research, academic, and
industry partners is just about to release Open MPI version 1.4 in reaction to
the GNU Libtool 2.2.6b security update release (see
http://security-tracker.debian.org/tracker/CVE-2009-3736 for more details).
This mail contai
ere - so it is working on NetBSD !
I am currently installing the PkgSrc build, having prevented the
install binary clash, and will post the results of that soon.
I have placed the tar of current patches from our PkgSrc build in
http://www.ecs.vuw.ac.nz/~kevin/forMPI/openmpi-1.3.4-20091208-netbsd.
Hi Matthew
More guesses/questions than anything else:
1) Is there any additional load on this machine?
We had problems like that (on different machines) when
users start listening to streaming video, doing Matlab calculations,
etc, while the MPI programs are running.
This tends to oversubscribe
On Tue, Dec 8, 2009 at 12:01 PM, Ross Boylan wrote:
> What is the difference between running a set of programs with
> independent invocations of mpirun vs specifying --app? The programs do
> not need to talk to each other.
>
> I think that if one job fails it will take the others down if I use
>
What is the difference between running a set of programs with
independent invocations of mpirun vs specifying --app? The programs do
not need to talk to each other.
I think that if one job fails it will take the others down if I use
--app. Is that correct? This is the main reason I'm considerin
I did the same test using 1.3.4 and still the same issue I also
tried to use the tm interface instead of specifying the hostfile, same
result.
thanks,
Jonathan
Josh Hursey wrote:
Though I do not test this scenario (using hostfiles) very often, it
used to work. The ompi-restart command t
Hi All,
I am having a problem running a couple of programs, ABySS and MrBayes in
parallel. I am using Linux Ubuntu 9.10 with a dual socket (Xeon 5520) machine.
There are 8 physical cores, or 16 with hyperthreading enabled.
I use openMPI version 1.3.4, plus a few other packages downloaded via
Whilst MPI has traditionally been run on dedicated hardware, the rise of
cheap multicore CPUs makes it very attractive for ISVs such as ourselves
(http://www.cambridgeflowsolutions.com/) to build a *single* executable
that can be run in batch mode on a dedicated cluster *or* interactively
on a
13 matches
Mail list logo
