From: Rick K. <rk...@nc...> - 2008-06-26 20:06:13
|
Abdullah - Please try to use the SourceForge mailing list for questions/comments about PerfSuite. That allows traffic to be archived that may benefit other people who have similar questions by browsing earlier postings. It also helps me keep my NCSA (work) email distinct, which in turn keeps my employer happy :) As far as your question goes: much is dependent on the particular MPI implementation and how it manages processes/tasks. For example, MPICH using the p4 device won't work with psrun at all (this was discussed in a perfsuite-users posting a long time ago). You may have to experiment with your own favorite MPI. Charm++ is another case that can work in some cases, others not. The driver for the processor's performance monitoring unit (perfmon or perfctr for Linux) takes care of virtualizing the hardware counter data on a per-thread basis, so if your application spawns separate processes that use multiple cores, they should each generate an output XML document. For multithreaded applications that use POSIX threads (either directly or through a Pthread-based interface like many OpenMP implementations), the option "-p" that psrun accepts will trap thread creation and generate per-thread performance data at thread exit. If you are instead looking for a system-wide monitoring tool that would track all cores over a given period of time, that is not what PerfSuite was intended to do, but there are other tools available that fill that space. Rick Abdullah Kayi wrote: > Hi Rick, > > I am pretty much getting the reasonable outputs from the tests that I > tried. So now, I am trying to use "psrun" with mpirun I couldn't find > an example for that other then cpi-mpi which works with libpshwpc. So > I am not sure what is needed for psrun to work for mpi or charm++ > directly. Also, how can I get theoutput from all the cores? Do you > have any ideas on these? Thanks so much for your help. > > Regards, > > Abdullah > > On Wed, Jun 25, 2008 at 5:39 PM, Abdullah Kayi <ap...@gm... > <mailto:ap...@gm...>> wrote: > > Ooops my bad, I shouldn't have used "psrun", now I am getting the > correct results. I will let you know about the ChaNGa results. > > On Wed, Jun 25, 2008 at 4:14 PM, Abdullah Kayi <ap...@gm... > <mailto:ap...@gm...>> wrote: > > Hey Rick, > > I am running the "hl" example like this; > > > psrun -c papi3_mflops.xml ./hl > > I am finally getting the xml output fine but when I look at > the results. > > Index > Description > Counter Value > ============================================================================================ > 1 Floating point > operations........................................ > 3 > 2 Total > cycles..................................................... > 629519 > > Event Index > ============================================================================================ > 1: PAPI_FP_OPS 2: PAPI_TOT_CYC > > There should be something wrong how come there were only 3 FP > operations in that output, I am using the "hl.c" as it is. Do > you have any ideas on this? > > Regards, > > Abdullah > > > |