Re: [PerfSuite-users] threshold

[Rick K. <rk...@nc...>]

Ryszard,

> Thank you for your concern and reply. Sorry it took a little whilre to get 
> back to your questions...

No problem, I appreciate your taking the time to update on the latest.

> I have tried both your suggestions. I have tested them with PerfSuite 
> 0.6.2.a3 and 0.6.2.a4. The profiling with the "profile.xml" config file works 
> for both versions!, but unfortunately the problem with a "real" config file 
> still remains. But, there is also a good news!. Because my simulation 
> produces some output files and for a long executions, the file size is quite 
> big (~300MB) I started run this simulation from the local hard drive instead 
> of using my home AFS directory, which I had used before in order to run a 
> simulation. After this movement my problem with a threshold has disappeared! 
> :) So, from my point of view the profiling works okay. Thank you again for 
> spending time on my questions!.

Hmmm!  This is good news although I am at a loss as to why there might be 
a difference depending on the filesystem in use.  Nevertheless, I am glad 
to hear that things are apparently working.  In your opinion, is this 
something that warrants inclusion in the BUGS file that is included in the 
PerfSuite distribution?  If so, I'd be happy to include in the hopes that 
it might save someone else a little detective work.

One thing I have seen before that sounds related is a difference in 
executable/library locations between the computer system on which the 
simulation is run versus the system on which the post-processing 
(psprocess) occurs.  What happened in that case is that the "<module>" 
element in the profiling XML output identified the location of the library 
through the "file" attribute in the context of runtime.  For example, 
instead of listing:

   <module file="/usr/lib/libsomething.so.0" offset="a5e000">

it had:

   <module file="/mnt/nfs/usr/lib/libsomething.so.0" offset="a5e000">

The result was that psprocess could not find the library as listed in the 
XML document and would not report any samples for that module.  The only 
workaround in this case was to correct the entries (using a text editor) 
before running psprocess.

Thanks again for the update and report,
Rick