[petsc-dev] Nested event logging and human friendly output

[Barry Smith]

  I'm sorry but I cannot determine how to display the output in a browser. From the manual it says:

If the xsl file is located in the same folder as the XML file, and if the files are located there as well, then the automatic conversion by the web browser results in a display such as Figure 1.

   but I have no idea what files the "_the_files_ are located there as well" means? 

  I now have two  files joe.xml that was generated by your code and begins with 

<!-- PETSc Performance Summary: -->
<petscroot>
  <runspecification desc="Run Specification">
    <executable desc="Executable">./ex1</executable>
    <architecture desc="Architecture">arch-debug</architecture>
    <hostname desc="Host">visitor097-045.wl.anl-external.org</hostname>
    <nprocesses desc="Number of processes">1</nprocesses>


and performance_xml2html.xsl  How, exactly, do I use these two files, opening either one in Chrome or Firefox produces nothing useful.

  Barry

   
> On Sep 14, 2015, at 7:45 AM, Koos Huijssen <koos.huijssen at vortech.nl> 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 koos.huijssen at vortech.nl
> web   www.vortech.nl
> ____________________________________________________________________
> 
> <timers.tar.gz>