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

wgcn updated FLINK-18715:
-------------------------
    Description: 
flink process add cpu usage metric,   user can determine that their job  is  io 
bound /cpu bound  ,so that they can increase/decrese cpu core in the container 
(k8s,yarn). If it's nessary 
.  you can assign  it  to me  ,I come up with a idea  calculating cpu usage 
ratio using   ManagementFactory.getRuntimeMXBean().getUptime() and  
ManagementFactory.getOperatingSystemMXBean().getProcessCpuTime  over a period 
of time .   it can get a value in single cpu core environment. and user can use 
the value  to calculate cpu usage ratio by dividing  num of container's cpu 
core.


  was:
flink process add cpu usage metric,   user can determine that their job  is  io 
bound /cpu bound  ,so that they can increase/decrese cpu core in the container 
(k8s,yarn). If it's necessary 
.  you can assign  it  to me 


> add cpu usage metric of  jobmanager/taskmanager  
> -------------------------------------------------
>
>                 Key: FLINK-18715
>                 URL: https://issues.apache.org/jira/browse/FLINK-18715
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Metrics
>    Affects Versions: 1.11.1
>            Reporter: wgcn
>            Priority: Major
>             Fix For: 1.12.0, 1.11.2
>
>
> flink process add cpu usage metric,   user can determine that their job  is  
> io bound /cpu bound  ,so that they can increase/decrese cpu core in the 
> container (k8s,yarn). If it's nessary 
> .  you can assign  it  to me  ,I come up with a idea  calculating cpu usage 
> ratio using   ManagementFactory.getRuntimeMXBean().getUptime() and  
> ManagementFactory.getOperatingSystemMXBean().getProcessCpuTime  over a period 
> of time .   it can get a value in single cpu core environment. and user can 
> use the value  to calculate cpu usage ratio by dividing  num of container's 
> cpu core.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to