aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik van Roode (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AURORA-660) Resource consumption display format for floats does not restrict #decimals
Date Fri, 22 Aug 2014 21:26:12 GMT

     [ https://issues.apache.org/jira/browse/AURORA-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Erik van Roode updated AURORA-660:
----------------------------------

    Description: 
Resource consumption displays CPU as a float without #decimal contraints, RAM and Disk with
2 decimals.

running 8 instances with Resources(cpu = 0.09, disk = 32*MB, ram = 64*MB)

viewing /scheduler/role

!resource display.png!

Formatting for CPU has way to many decimals,.

Formatting is done in src/main/resources/org/apache/aurora/scheduler/http/ui/js/filters.js

The scaleMb function doesn't seem to ever create numbers that aren't effectively integer (integer
division truncates to int?),
I'd argue RAM/Disk could just use zero decimals.

 toCores is missing a ".toFixed(N).toString()" after the "return count", where N could be
2 or 3. I'd think 2 would be good.

Output could look like this (less clutter)

!new display.png!

  was:
Resource consumption displays CPU as a float without #decimal contraints, RAM and Disk with
2 decimals.

running 8 instances with Resources(cpu = 0.09, disk = 32*MB, ram = 64*MB)

viewing /scheduler/role

!resource display.png!

Formatting for CPU has way to many decimals,.

Formatting is done in src/main/resources/org/apache/aurora/scheduler/http/ui/js/filters.js

The scaleMb function doesn't seem to ever create numbers that aren't effectively integer (integer
division truncates to int?),
I'd argue RAM/Disk could just use zero decimals.

 toCores is missing a ".toFixed(N).toString()" after the "return count", where N could be
2 or 3. I'd think 2 would be good.






> Resource consumption display format for floats does not restrict #decimals
> --------------------------------------------------------------------------
>
>                 Key: AURORA-660
>                 URL: https://issues.apache.org/jira/browse/AURORA-660
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Erik van Roode
>            Priority: Minor
>         Attachments: new display.png, resource display.png
>
>
> Resource consumption displays CPU as a float without #decimal contraints, RAM and Disk
with 2 decimals.
> running 8 instances with Resources(cpu = 0.09, disk = 32*MB, ram = 64*MB)
> viewing /scheduler/role
> !resource display.png!
> Formatting for CPU has way to many decimals,.
> Formatting is done in src/main/resources/org/apache/aurora/scheduler/http/ui/js/filters.js
> The scaleMb function doesn't seem to ever create numbers that aren't effectively integer
(integer division truncates to int?),
> I'd argue RAM/Disk could just use zero decimals.
>  toCores is missing a ".toFixed(N).toString()" after the "return count", where N could
be 2 or 3. I'd think 2 would be good.
> Output could look like this (less clutter)
> !new display.png!



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message