Thank you for contributing the nested logging. I have incorporated into the 
PETSc branch barry/xml-nested-logging  if you look at  
https://bitbucket.org/petsc/petsc/commits/bb1d7374b64f295b2ed5ff23b89435d65e905a54?at=master
 you can see exactly what I have incorporated into PETSc.  I will merge it into 
next for portability testing in the next couple of days. I expect over time as 
I understand it better I will be able to improve its integration with PETSc.  
Currently to generate the nested logging it is as simple to use as -log_view 
:filename.xml:ascii_xml

  Thanks again,

   Barry





> On Sep 14, 2015, at 7:45 AM, Koos Huijssen <[email protected]> wrote:
> 
> Dear PETSc development team,
> 
> We have developed an extension of the PETSc event logging facilities that has 
> the following advanced features:
> 
> - It allows logging of events in the form of a nested tree. So if some 
> function is called from multiple locations in the code, these instances are 
> distinguished. This in contrast with the standard event logger, which only 
> logs the amount of total call time.
> - It allows the output report to be formatted in XML format. This output can 
> then be viewed in a human-friendly form in a web browser
> with the use of the XSL Transformation script performance_xml2html.xsl. The 
> html features an nested timings tree that can be expanded and collapsed as 
> desired.
> 
> This tool has been very useful for us to analyze the code and pinpoint 
> performance bottle necks. We think that it can be useful for others as well, 
> and therefore we are providing the code here for integration in the open 
> source distribution of PETSc.
> 
> For more information I refer to the included manual. We have also provided a 
> test program and a makefile for convenience. The test program can be run 
> using MPI with for instance 3-6 processes.
> 
> I apologize for not using the git repo to submit the developed code. I also 
> apologize for not adhering to the PETSc coding standards (or at least not as 
> far as I know), but I hope that it is not too far off.. Apart from the whole 
> capital/underscore standardization stuff one issue may require special 
> attention, namely the (ab)use of the format PETSc_VIEWER_ASCII_IMPL for 
> signaling the XML format in XMLViewer.c. I couldn't find an already existing 
> and better fitting format, but it could be necessary to add a new format here 
> for this purpose.
> 
> Can you take it up from here and realize the integration of the code in the 
> PETSc distribution?
> 
> With kind regards,
> 
> Koos Huijssen
> 
> -- 
> ____________________________________________________________________
> 
> VORtech BV - Scientific software engineers
> ____________________________________________________________________
> 
> Dr.ir. Koos Huijssen
> 
> P.O. Box 260
> 2600 AG Delft
> The Netherlands
> 
> phone  +31(0)15-285 0125
> mobile +31(0)6-3333 0803
> email [email protected]
> web   www.vortech.nl
> ____________________________________________________________________
> 
> <timers.tar.gz>

Reply via email to