Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • duniter duniter
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 190
    • Issues 190
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nodes
  • typescript
  • duniterduniter
  • Merge requests
  • !1211

Closed
Created Dec 02, 2017 by vincentrou@vincentrouDeveloper
  • Report abuse
Report abuse

Add eco mode

  • Overview 1
  • Commits 1
  • Changes 6

This MR uses the number of test per second to evaluate if the duniter is too fast (I set it to 300 test/s for now : it is one of my i7 core at 30% of CPU usage). At first the eco mode reduce number of cores and when there is only one core left it reduce CPU usage.

For now the configuration is not saved so if the node is restarted the config will comeback to the initial state.

Any remark is welcome !

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: reduce_cpu