In the past, I've had the best success with Google's gperftools.  I
know that Greg has used them recently also.

-- Sung

On Thu, Jun 04, 2015 at 09:42:34AM -0700, Brad Chamberlain wrote:
> 
> Some developers have had some success with Rice's HPC Toolkit as well, I 
> believe.
> 
> -Brad
> 
> 
> On Thu, 4 Jun 2015, Michael Ferguson wrote:
> 
> > Hi Hui -
> >
> > Are you trying to use gprof? How are you monitoring the performance?
> >
> > AFAIK, gprof in particular just doesn't work with multiple threads...
> > I've heard that the profiler with gperftools works better,
> > but I don't have any experience with it myself.
> >
> > Cheers,
> >
> > -michael
> >
> > On 6/4/15, 12:13 PM, "Hui Zhang" <[email protected]> wrote:
> >
> >> Hello,
> >>
> >>
> >>
> >> I was trying to monitor the performance of a simple Chapel code, but even
> >> I don't use parallelism in the code(like forall, coforall...), just as
> >> simple as a single-thread C program,
> >> I found Chapel still creates a worker thread for the user code, and the
> >> master thread to initialize and finalize the program. Therefore, I want
> >> to know :
> >>
> >> 1. When and how the worker thread is spawned ?
> >> 2. What's your suggestion to monitor the worker thread since all I'm
> >> getting now is from the master thread, which isn't useful to me.
> >>
> >> 3. Further, if parallelism is used(like forall,etc), is there any way to
> >> monitor all the threads ?
> >>
> >>
> >>
> >> Thanks
> >>
> >>
> >>
> >> --
> >> Best regards
> >>
> >>
> >> Hui Zhang
> >>
> >>
> >
> >
> > ------------------------------------------------------------------------------
> > _______________________________________________
> > Chapel-developers mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/chapel-developers
> >
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Chapel-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/chapel-developers

------------------------------------------------------------------------------
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers

Reply via email to