Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • N nrm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • argo
  • nrm
  • Issues
  • #12
Closed
Open
Issue created Aug 07, 2018 by Sridutt Bhalachandra@sriduttbContributor3 of 3 checklist items completed3/3 checklist items

Add application-level power profiling support

Need to add application-level power profiling support to allow NRM to report application run power/energy profiles. This is required to assess the effectiveness and impact of power policies currently in NRM and that will be added in the future.

A possible solution is to use SensorManager measure the initial and final values. The difference in values can be reported as a part of the application 'exit' event.

Note: This is a very basic solution and does not handle multiple containers/applications. Will have to fix this in the future.

Tasks involved:

  • Add an option to manifest file to enable profiling
  • Make changes in SensorManager to allow ​calculation of the difference in measured (stored) values using rapl_reader functions
  • Make changes in NRM to display profiling information at the end of an ​application run
Edited Aug 14, 2018 by Sridutt Bhalachandra
Assignee
Assign to
Time tracking