Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.core beat.core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.corebeat.core
  • Issues
  • #43
Closed
Open
Issue created Sep 06, 2015 by André Anjos@andre.anjos💬Owner

Statistics output by agent don't account for the CPU time spent reading data from disk

This is inconsistent with our cpulimit policy, for which we are stipulating both the agent and the user process are bound to the same CPU limit and must share the resources.

In this way, it would be best if we'd also account the CPU usage from the agent + the user process on the final statistics output.

One must be careful as the agent is called in two different contexts (beat.scheduler iodaemon or beat.cmdline exp run), but the accounting must always come out right.

Assignee
Assign to
Time tracking