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

Confusing measure for CPU usage #405

Closed
fwalker opened this issue Feb 19, 2016 · 3 comments
Closed

Confusing measure for CPU usage #405

fwalker opened this issue Feb 19, 2016 · 3 comments
Assignees

Comments

@fwalker
Copy link

fwalker commented Feb 19, 2016

The unit for measuring the CPU usage - "mCPU" - hard to understand. Our K8s Ops as well as myself could not guess the meaning until @cheld let us know it's "milli CPU".
mili
Some options:

  1. Enhance the tool-tip
  2. Change the label to "‰ CPU"
@bryk bryk added this to the v1.0 milestone Feb 19, 2016
@bryk
Copy link
Contributor

bryk commented Feb 19, 2016

@bgrant0607 How should we display CPU usage to users?

The more I think about this the more I'm in favor of changing X mCPU to 0.00X cores. This is exactly what the spec says: https://github.com/kubernetes/kubernetes/blob/master/pkg/api/v1/types.go#L2175. This means we're not introducing anything new. Also, the value Y cores is easier to understand than Z mCPU.

Your opinions?

@cheld
Copy link
Contributor

cheld commented Feb 19, 2016

One more idea. What about:

0.00X CPU(s).

This is slightly incorrect. So, we explain it somehow in the tooltip. e.g.

Display:
2.5 CPUs

Tooltip: (.... uses 2.5 CPU cores)

@bgrant0607
Copy link
Member

I'm fine with showing CPU as a decimal. I'd make CPU singular.

We should expect double-digit numbers of cores.

@bryk bryk self-assigned this Mar 4, 2016
bryk added a commit to bryk/dashboard that referenced this issue Mar 4, 2016
With that we'll not have `kcores` (kilo-cores) neither `TCPU`
(tera-CPU). This also saves space since all numbers in a column have the
same unit.

Fixes kubernetes#405
bryk added a commit to bryk/dashboard that referenced this issue Mar 7, 2016
With that we'll not have `kcores` (kilo-cores) neither `TCPU`
(tera-CPU). This also saves space since all numbers in a column have the
same unit.

Fixes kubernetes#405
@bryk bryk closed this as completed in #493 Mar 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants