Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 425
    • Issues 425
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

Planned maintenance at 14:00 - platform may be offline until 15:00 (UK times)

  • Development
  • openfoamopenfoam
  • Issues
  • #441
Closed
Open
Issue created Mar 28, 2017 by Admin@OpenFOAM-adminMaintainer

Minor improvements to profiling

First patch has two minor improvements:

  • Make it possible to switch on profiling via site/vXXX+/controlDict (I like to always have profiling)
  • For multi-region cases add the region-name to the name of the profiling-information

profilingImprovements.patch

The second patch adds profiling to the time loop by deleting/creating a new profiling::Trigger-object at every call to run(). That way in the profiling information it can now be seen how much time was spent inside and outside the time-loop (usually should be in the order of 99% to 1). The ProfilingTrigger-class was necessary as apparently C++ does not allow the forward-declaration of interior classes like profiling::Trigger

profilingProfileTimeLoop.patch

I split this into two patches because obviously fiddling with the Time-class is always controverial

Assignee
Assign to
Time tracking