Gary, On Fri, Apr 18, 2008 at 7:03 PM, <[EMAIL PROTECTED]> wrote: > > I had downloaded the perfmon2 package but have not installed them yet. My > understanding
Which packages are you talking about here? > > Unfortunately our customer is in a secure environment and therefore all I > have is a copy of the > binary executable for the application. It took us 3 months and a non > disclosure agreement with them > to even get that much. Since I do not have source I can not modify the > application to skip doing the > fork/exec's. That's all right. We should not need to know about what the application is doing. We can figure out whether it is forking or not and how many children. That should be all we need to know. > > As Stephane pointed out in another email on this chain, pfmon (by default) > does not count > events for the forked processes. The values reported by pfmon when used > in sampling > mode seem to account for the CPU time used by the applicaiton, When pfmon > is run in sampling > mode on this application it reports 4788780 samples. When hpcrun is used > it only reports 41602 > samples (in the code.exe data file). Both of these runs were done with a > sample period of 32767. > For the pfmon samples, you mean with --follow-all and --overflow-block? What you should do is correlate the number of samples with the duration of each process. If I recall pfmon can give the real time of a process if you pass the --show-time option. Don't remember if this works with --follow-all, though. Keep in mind that there will be blind spots with non-self sampling. Knowing that PAPI is all self-monitoring (self-sampling) I am surprised to see such a low count with hpcrun. As Phil mentioned, it is likely a problem with PAPI during fork when sampling. > Excerpts from this grep output follows: > > Apr 8 15:33:22 molson kernel: pfm_mask_monitoring.928: CPU0 [18168] > pmc[4]=0x801220 > Apr 8 15:33:22 molson kernel: pfm_restore_monitoring.1013: CPU0 [18168] > [18168] pmc[4]=0x801228 > Apr 8 15:33:22 molson kernel: pfm_mask_monitoring.928: CPU0 [18168] > pmc[4]=0x801220 > Apr 8 15:33:22 molson kernel: pfm_mask_monitoring.928: CPU0 [18168] > pmc[4]=0x801220 > Don't recall if you should be alarmed by the double mask-monitoring. I have not looked at the v2.0 codebase in a very long time. I'll check quickly. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ perfmon2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
