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
There is another tool named "Cloud-Carbon-Footprint", here. It reads nodes from AWS cost report (or any other cloud provider), makes an educated guess about the load and calculates CO2eq consumption, utilizing everything known about the data center, including cooling, location, embodied carbon. So it less exact than kepler for the load, but more exact about additional factors.
Our idea would be to combine both tools, stripping the load assumptions from CCF and replacing them with kepler measurements. Is this idea correct from your point of view, i.e. no part of the consumption is counted twice?
Can someone help this idea along in any way?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
There is another tool named "Cloud-Carbon-Footprint", here. It reads nodes from AWS cost report (or any other cloud provider), makes an educated guess about the load and calculates CO2eq consumption, utilizing everything known about the data center, including cooling, location, embodied carbon. So it less exact than kepler for the load, but more exact about additional factors.
Our idea would be to combine both tools, stripping the load assumptions from CCF and replacing them with kepler measurements. Is this idea correct from your point of view, i.e. no part of the consumption is counted twice?
Can someone help this idea along in any way?
Beta Was this translation helpful? Give feedback.
All reactions