[ET Trac] [Einstein Toolkit] #791: Output timer tree as XML

[Einstein Toolkit]

#791: Output timer tree as XML
--------------------------+-------------------------------------------------
  Reporter:  hinder       |       Owner:  eschnett   
      Type:  enhancement  |      Status:  reviewed_ok
  Priority:  minor        |   Milestone:             
 Component:  Carpet       |     Version:             
Resolution:               |    Keywords:             
--------------------------+-------------------------------------------------

Comment (by eschnett):

 The way to access the current iteration or coordinate is via cctkGH. One
 could store this in a global variable when a function is called from the
 scheduler, and access it from there, but this does not seem elegant --
 could cctkGH instead be passed to the timer?

 > Each time is stored in a vector<double> every time the timer is stopped.
 Could this be a problem?

 Yes, definitely. What if there are hundreds of timers and tens of
 thousands of iterations? This would require many megabytes of storage.
 Some timers may even be called many times per iteration; we cannot assume
 that a timer is only called once per iteration. This also makes calling
 timers very expensive, as they may have to allocate storage. This needs to
 be disabled unless explicitly enabled by a parameter.

-- 
Ticket URL: <https://trac.einsteintoolkit.org/ticket/791#comment:5>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit