Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • gnome-system-monitor gnome-system-monitor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 130
    • Issues 130
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • gnome-system-monitorgnome-system-monitor
  • Issues
  • #85
Closed
Open
Issue created Aug 07, 2018 by Ghost User@ghost

Better handling for high CPU counts

It appears the CPUs in the resources tab is capped to 50 CPUs, which is entirely reasonable, but some high end devices have more than 50 logical cores. Additionally, it might be worth investigating randomizing the graph color for CPUs after the first four.

Screenshot of CPU section showing only 50 Cores

Assignee
Assign to
Time tracking