[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] Prepending MPI Launch Command
|
The initial use-case for this is the Scalasca performance analysis system. One of their utilities is put before the 'mpirun' or equivalent command. It's a sequential program that starts the first parallel job with the given executable, and then starts a second parallel job after the first returns, to do parallel analysis of the performance data generated by the application run.
On the command line if you do:
scan -t mpirun -np 4 a.out <arguments to a>
Scalasca will first execute "mpirun -np 4 a.out <arguments to a>" and then "mpirun -np 4 scout..mpi <trace data>"
It's possible that this could be accomplished in a workflow, since what "scalasca -analyze" does can be done manually. But I believe there are a couple tools out there that fit this model and it'd be nice to be able to support them directly.
Regards,
Wyatt Spear
On Mon, Nov 30, 2009 at 9:51 AM, Dave Wootton
<dwootton@xxxxxxxxxx> wrote:
Wyatt
Is this tool an MPI application or is it just a simple C/C++ application?
Are you expecting to invoke a single copy of the tool or is there a copy
of the tool for each MPI task?
If you're expecting a single tool task which in turn launches the MPI
application, the PE plugin won't support that today. What it will do is
launch 'n' copies of your tool, where 'n' is the number of application
tasks you requested. In turn, I think you get one MPI task per tool
instance.
You can't fix that by specifying just a single task because then you will
have only a single application task as well.
In order to make this work, I think we need to have a way for the plugin
to invoke the tool as a non-PE process and then for the plugin to walk
down the process tree to find the poe process it needs to properly track
the application status. If we need to make this work, this is where I
think we need to start, although there might be more problems to be found.
Dave
From:
To:
Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx>
Date:
11/25/2009 05:24 PM
Subject:
[ptp-dev] Prepending MPI Launch Command
Sent by:
ptp-dev-bounces@xxxxxxxxxxx
Greetings,
There are a few parallel performance tools which need to be composed with
the mpirun (or equivalent) command. On the command line this might look
like:
performance_tool mpirun -np 4 mpi_app
Is there any way that this could be supported with the PTP launch system?
I am not really familiar with the resource manager API but I am guessing
that this would have to be done for each resource manager implementation.
I'll start looking through the code myself pretty soon but if anyone
could point me in the right direction I would really appreciate it.
Similarly, if this is a non-starter for some reason it'd be good to know
before I start.
Thanks,
