You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, usage impacts are measured by multiplying a duration, an impact factor, and an electrical consumption : impact = electrical_consumption*duration*impact_factor
We focus in this issue on how to identify electrical_consumption.
There are 2 ways today in the API :
Given by the user, in case the user has a sensor like boagent, scaphandre or a wattmeter. We should keep this behavior.
Using a Workload object which links a percentage of workload to an electrical consumption. See doc for more info.
If the user have the electrical consumption he can use this type of query :
This is kind of dump since the user could directly provide the electrical consumption following the first method.
If the user doesn't have his electrical consumption (which is the normal case), he can provide a workload object without power. The power will be smart completed. We use this behavior in the case of AWS instances with Teads punctual consumption profile.
We can only use a specific load repartition : [idle, 10, 50, 100] (In some cases, we only have min and max value, we could have more precise repartition in the case of stress test for instance)
We cannot give a specific workload (for example My server have been running at 34% for 2 hours)
The workload object is hard to understand and manipulate
Solution
Instead of having punctual workload objects we should use functions generated from the regression of punctual measures.
The idea is to use a functions : workload_to_electrical_conso which returns an electrical consumption from a given workload : workload_to_electrical_conso(workload(%)) = electrical_consumption
TODO
Since this problem is complex it will be divided into several issues
Context
Today, usage impacts are measured by multiplying a duration, an impact factor, and an electrical consumption :
impact = electrical_consumption*duration*impact_factor
We focus in this issue on how to identify
electrical_consumption
.There are 2 ways today in the API :
Given by the user, in case the user has a sensor like boagent, scaphandre or a wattmeter. We should keep this behavior.
Using a Workload object which links a percentage of workload to an electrical consumption. See doc for more info.
If the user have the electrical consumption he can use this type of query :
This is kind of dump since the user could directly provide the electrical consumption following the first method.
If the user doesn't have his electrical consumption (which is the normal case), he can provide a workload object without power. The power will be smart completed. We use this behavior in the case of AWS instances with Teads punctual consumption profile.
Limits
With such behavior :
min
andmax
value, we could have more precise repartition in the case of stress test for instance)My server have been running at 34% for 2 hours
)Solution
Instead of having punctual workload objects we should use functions generated from the regression of punctual measures.
The idea is to use a functions : workload_to_electrical_conso which returns an electrical consumption from a given workload :
workload_to_electrical_conso(workload(%)) = electrical_consumption
TODO
Since this problem is complex it will be divided into several issues
The text was updated successfully, but these errors were encountered: