Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make system timing correct with unscheduled execution #4583

Commits on Jul 8, 2014

  1. Use C++11 constructs for CPUTimer

    Needed move semantics to allow CPUTimer to be placed in containers.
    Dr15Jones committed Jul 8, 2014
    Configuration menu
    Copy the full SHA
    8915104 View commit details
    Browse the repository at this point in the history
  2. Use SystemTimeKeeper to generate timing summary

    In order to properly account for unscheduled execution, the summary timing is now done by SystemTimeKeeper. This way the summary can reuse the signals sent by the ActivityRegistry which includes the signals sent when an unscheduled execution is being triggered.
    Dr15Jones committed Jul 8, 2014
    Configuration menu
    Copy the full SHA
    6d303dd View commit details
    Browse the repository at this point in the history
  3. Only run one timer for module and module on path

    Reuse the timing measurement made for a module when doing the time accounting for the time a module spends running on a particular path. This avoids having two separate timers running.
    Dr15Jones committed Jul 8, 2014
    Configuration menu
    Copy the full SHA
    b98d2c5 View commit details
    Browse the repository at this point in the history

Commits on Jul 9, 2014

  1. Removed old timing summary infrastructure

    Removed the timing infrastructure which was previously used to generate the timing summary. This is no longer needed by the new way of getting the timing summary.
    Dr15Jones committed Jul 9, 2014
    Configuration menu
    Copy the full SHA
    4ab074f View commit details
    Browse the repository at this point in the history