Agenda

• Profiling Tool
  • Legacy profiling tool implemented in PR #936. Results look like this and this
  • Design discussion for Sharrow version of tool in issue #937.
  • Questions:
    1. Is the HTML summary output sufficient and/or desirable? Or, is some other aggregation of the results needed?
    2. Any feedback on design discussion? (If so, please comment on the issue.)

Technical

• Expression Profiling
  • To use just put in "expression_profile: true"
    • Use in development mode; not needed for production mode
  • Additional folder added to output folder that produces hundreds of log files that provides run time for each model/step
  • Includes two summary output files; can be sorted;
  • This is for non-Sharrow
  • Utilize log and summary files to assess what can be adjusted and optimized for faster run times
  • Beyond scope of task to actually optimize any of the steps and model components
  • Can be utilized on multi-process version; separate directory for each sub-processor
  • Suggested next steps: Get a group together to use log file to identify issues and divy up issues to address between individual/teams within the group
  • David H assigned to review in about 2 weeks
• Solution with Sharrow
  • Please review what Jeff has written about design of Sharrow profiler
• Review roadmap by end of week