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
Currently the SCI calculation in the Green Metrics Tool has some limitations:
The SCI is only calculated for the total [RUNTIME] phase
This should be improved to have it separately for every phase
It is not immediately visible which variables have been used to derive the score. They are all present in the interface, but in various and undocumented locations
The I, M etc. parameters are under the Machine Tab
The R values are in the logs tab. Which is also deleted after a certain retention period (TBD: in the future)
See screenshots for both locations as example
Technically the SCI is currently handed over internally as variable. It would however be more consistent if the SCI is an actual reporter that would depend on a machine energy reporter and a CO2-grid-intensity reporter to be present
The R-Values have to come from the application itself though. Currently we use a buffered output stream from the container to the host OS which is then parsed for the variables. It would be better however to have a pre-defined output location inside of the container, something like /tmp/green-metrics-tool/sci/R.log that the user can send these values in the instrumented application to. The gain here is that the stdout is not overloaded and the unnecessary noise is not captured on top.
Screenshots of SCI and location
The text was updated successfully, but these errors were encountered:
Currently the SCI calculation in the Green Metrics Tool has some limitations:
/tmp/green-metrics-tool/sci/R.log
that the user can send these values in the instrumented application to. The gain here is that the stdout is not overloaded and the unnecessary noise is not captured on top.Screenshots of SCI and location
The text was updated successfully, but these errors were encountered: