You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe the problem you are trying to solve.
preCICE contains its own profiling framework.
It could be useful for the user to use this profiling functionality as well.
This would add information to the solver sections solver.initialize and solver.advance, making them easier to interpret, especially in traces.
This would be especially useful to integrate the time measurements of existing adapters.
The limitation being that preCICE needs to be constructed for the profiling to work.
This nicely fits the future plans to standardize adapters. Very similar idea (but probably worth a separate issue one day): We could do the same for our logging.
Please describe the problem you are trying to solve.
preCICE contains its own profiling framework.
It could be useful for the user to use this profiling functionality as well.
This would add information to the solver sections
solver.initialize
andsolver.advance
, making them easier to interpret, especially in traces.This would be especially useful to integrate the time measurements of existing adapters.
The limitation being that preCICE needs to be constructed for the profiling to work.
Describe the solution you propose.
Describe alternatives you've considered
Solver codes may already rely on external tools, or other kind of instrumentalization for profiling.
Additional context
See #1419
The text was updated successfully, but these errors were encountered: